Vue 3.6 brings Vapor mode. You add one word to a component:
<script setup vapor >
Enter fullscreen mode
Exit fullscreen mode
and Vue compiles it to code that updates the DOM directly, with no virtual DOM. Faster updates, smaller bundle. Sounds great.
But not every feature and not every library works in a Vapor component yet. And the worst failures make no sound. The build passes. The console is empty. A button stops opening its dialog, and you find out in production.
A real example
Take a shadcn-vue dialog. Under the hood it uses as-child from Reka UI. With Vue 3.6.0-rc.14 and older, as-child inside a Vapor component does not pass attributes or listeners to the child. The button renders fine. It just has no click listener.
It's fixed in Vue 3.6.0-rc.15 now. But that one bug says a lot. If this one gives no sign at all, how many others are out there? And how do you find them before your users do?
Clicking through every page after each change is not a plan.…