# vue/release
Vue v3.6.0-rc.1
importance: highbreakingmigrationfeatureprerelease
Vue 3.6 introduces Vapor Mode, a new compilation mode for Single-File Components (SFCs) aimed at reducing bundle size and improving performance. The reactivity system has been refactored based on alien-signals, enhancing performance and memory usage.
affected
Developers using Vue for performance-sensitive applications or those interested in reducing bundle size are affected.
action
Consider adopting Vapor Mode for new or performance-critical parts of your application.
release_signals
-Options API is not supported in Vapor Mode
-`getCurrentInstance()` returns `null` in Vapor components
-Component template refs do not expose properties like `$el`, `$props`, `$attrs`, `$slots`, and `$refs`
-Custom directives in Vapor use a different interface
-`slots.default()` is not a side-effect-free inspection API in Vapor
+Introduction of Vapor Mode for SFCs
+Refactor of `@vue/reactivity` based on alien-signals
+Support for template-only SFCs and `<script setup>` in Vapor Mode
+Creation of pure Vapor applications with `createVaporApp()`
+VDOM interop via `vaporInteropPlugin`
migration_steps5 steps
- 01Use `createVaporApp()` for pure Vapor applications
- 02Install `vaporInteropPlugin` for VDOM interop
- 03Avoid calling `slots.default()` to inspect output before rendering
- 04Use distinct regions in an app for Vapor and VDOM components
- 05Bypass event delegation for direct event handling
code_snippet
```vue
<script setup vapor>
// ...
</script>
```# community_signal
How useful is this release to your stack?
—
net score
Sign in with GitHub to cast your vote.
Sign in with GitHub to vote
You’ll return to this release, then choose your vote.