Evan You

Sorry, looking at this, it should be considered a legit bug. Also adjusted the priority.

I like the direction of ``` import('some_cjs_module.js').then(__toESM) ``` The downsides seem like a reasonable trade-off to me. Just want to make sure we can avoid the `__toESM` when we know...

Just a note this may have to do with `v-model` preventing temporary updates during a composition (which is necessary for some input methods e.g. Chinese) - and some devices may...

Superseded by 63689ed @skirtles-code that seems to be a separate topic from this PR - the current behavior of Vue custom elements always reflect declared props as attribute if it...

This adds quite a bit of extra logic - it'd be nice to see a benchmark of how this affects the cases it's optimizing for, and whether it affects other...

Rolldown already implements in-memory incremental build (which we haven't documented yet). We can reuse the same logic to implement file-system based **persistent build**. This is something we have planned but...

This has to be fixed in `@vue/repl` as the patching happens here https://github.com/vuejs/repl/blob/main/src/output/srcdoc.html#L158 Maybe we can workaround this by stringifying + postMessage in an async tick.

closed via 63689ed77 (to be released in 3.5)

@ysj16 I'm not yet fully convinced that this is the best syntax to go with. I think a proper RFC with more discussion around the use case would be needed.

I agree with @skirtles-code here - this change essentially makes the `:global()` work like a combinator instead of a functional pseudo class. The combinator-like behavior of `:deep` has been deprecated...