$ the-wire · showcase
KeepAlive root propagation lands in vue-jsx-vapor
By RepoJournal · Filed · About Vue.js · Composed from the cited sources · methodology
1 person shipped this
vue-jsx-vapor spent the day porting Vue core compiler fixes into its Vapor path, tightening KeepAlive root handling, tooling aliases, and how block keys are threaded through component creation.
fix(compiler/vapor): propagate component root through KeepAlive vuejs/vue-jsx-vapor
vue-jsx-vapor's compiler now propagates the component root through KeepAlive, copied from the equivalent fix in Vue core. If you nest components under KeepAlive in Vapor mode, this is the change that governs which root the compiler sees.
fix(macros/volar): remove defineComponent alias vuejs/vue-jsx-vapor
The macros/Volar fix removes the defineComponent alias, so Volar no longer resolves JSX components through that alias path. Editor type-checking and completion for defineComponent-authored components in JSX files is what shifts.
refactor(compiler/vapor): pass component keys through their creation vuejs/vue-jsx-vapor
Compiler keys are now passed through their creation calls rather than applied via setBlockKey, another port of a Vue core change. It is an internal refactor, but it rewrites how block keys reach components at compile time.
chore: remove valueAsNumber dynamic key and test vuejs/vue-jsx-vapor
valueAsNumber is gone as a dynamic key, along with its test, narrowing the set of input properties the compiler treats as dynamic. If you were relying on valueAsNumber bindings through the dynamic path, verify the behavior in your own build.
