v3.6.0-alpha.1
Vue 3#vue #vue3
FeaturesPerformance Improvements
- reactivity: refactor reactivity core by porting alien-signals (#12349) (313dc61)
Bug Fixes
- css-vars: nullish v-bind in style should not lead to unexpected inheritance (#12461) (c85f1b5), closes #12434 #12439 #7474 #7475
- reactivity: ensure multiple effectScope
on()andoff()calls maintains correct active scope (#12641) (679cbdf) - reactivity: queuing effects in an array (#13078) (826550c)
- reactivity: toRefs should be allowed on plain objects (ac43b11)
- scheduler: improve error handling in job flushing (#13587) (94b2ddc)
- scheduler: recover nextTick from error in post flush cb (2bbb6d2)
About Vapor Mode
Vapor Mode is a new compilation mode for Vue Single-File Components (SFC) with the goal of reducing baseline bundle size and improved performance. It is 100% opt-in, and supports a subset of existing Vue APIs with mostly identical behavior.
Vapor Mode has demonstrated the same level of performance with Solid and Svelte 5 in 3rd party benchmarks.
General Stability NotesVapor Mode is available starting in Vue 3.6 alpha. Please note it is still incomplete and unstable during the alpha phase. The current focus is making it available for wider stability and compatibility testing. For now, we recommend using it for the following cases:
- Partial usage in existing apps, e.g. implementing a perf-sensitive sub page in Vapor Mode.
- Build small new apps entirely in Vapor Mode.
We do not recommend migrating eixsting components to Vapor Mode yet.
Pending FeaturesThings that do not work in this version yet:
- SSR hydration* (which means it does not work with Nuxt yet)
- Async Component*
- Transition*
- KeepAlive*
- Suspense
Features marked with * have pending PRs which will be merged during the alpha phase.
Opting in to Vapor ModeVapor Mode only works for Single File Components using

Generated by RSStT. The copyright belongs to the original author.