Defaults to TS for `

Question

Discussion: Should lang default to

Ubugeeei · Answer

Wouldn't it be a high cognitive load for users if the interface is not aligned with ot

icarusgk · Answer

I think we should keep Vapor's behavior predictable. Replacing the <code class="notran

pavi2410 · Answer

How about<div class="highlight highlight-source-js notranslate position-relative

LittleSound · Answer

I really like Type, and I use it in almost all of my projects. However, the inco

bencodezen · Answer

Type should not be the default for Vapor mode because it breaks the fundamental

sxzz · Answer

It's worth mentioning that TS can essentially be considered a superset of JS. Enabling

neneodonkor · Answer

I think we should keep Vapor's behavior predictable. Replacing the

suisuiz · Answer

I think TS should not be the default.

kiaking · Answer

My opinion aligns with <a class="user-mention notranslate" data-hovercard-type="user"

fimion · Answer

Unless lang="ts" is a requirement for vapor mode, the

unpseudocomplique · Answer

One of the vue main sell point is easy adoption.
This would make it harder for jun

Ubugeeei · Answer

There may be two ways to indicate attributes, where to focus on them?
(It's quite

Ubugeeei · Answer

Because Vapor does not intend to support non-setup SFCs.

michaelpumo · Answer

I have to echo what <a class="user-mention notranslate" data-hovercard-type="user" dat

sxzz · Answer

About non-setup s, I haven't figured this out yet, let's leave this topic for an

MuhammadM1998 · Answer

Couldn't it be a compiler option that defaults to lang=js

baseballyama · Answer

We would like Vue users to use vapor as soon as possible. However, until it stabilises

eunjae-lee · Answer

I'd be happy to have a global config on this, and let individual component decides wha

neneodonkor · Answer

<blockquote>How about<div class="highlight highlight-source-js notranslate posit

sxzz · Answer

RihanArfan · Answer

From my understanding, Vapor requires a build step to compile into runtime code. Given

fimion · Answer

I will also point out that this would be the only instance (I can think of) in a sfc w

neneodonkor · Answer

Because Vapor does not intend to support non-setup SFCs.

Ubugeeei · Answer

pickup some tweets of vuejs team

cyhnkckali · Answer

I think the default ts would break the retrospective process. It makes the most sense;

Defaults to TS for `<script vapor>` about core-vapor HOT 25 OPEN