Vue.js: Vapor Renderer's Teardown Troubles
Four fixes landed today targeting state that gets lost when components are cached, nested, or paused mid-transition — with three of the four PRs hitting the runtime-vapor renderer's handling of KeepAlive and nested branches.
Duration: PT2M23S
Episode overview
This episode is a short developer briefing from Vue.js.
It explains recent repository work in plain language.
- Show: Vue.js
- Published: 2026-08-14T13:10:59Z
- Audio duration: PT2M23S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good day, and welcome to the Vue.js briefing for August 14th, 2026.
Today's activity has a clear center of gravity: components that get cached or nested are losing track of their own state, and the vapor renderer is where most of the fixing is happening.
Three separate PRs from edison1105 all touch KeepAlive behavior under nested conditions. PR 15293 fixes cached input effects getting torn down when they shouldn't — the solution moves those effects into a scope owned by the cache itself, so it can pause and resume properly instead of stopping dead when a branch…
The fourth item, PR 15294, is a Suspense fix but touches a similar nerve: transition appear hooks nested inside a pending Suspense branch weren't firing correctly, and could even get silently replaced by an update while still pending. The fix tracks deferred transitions by element and branch, then fires the right…
What's next: watch for follow-up hardening around vapor mode's scope handling, since 15296 is described as a broad change touching many areas — broad refactors like that tend to surface edge cases quickly. If you work with KeepAlive and nested conditionals, these merges are worth pulling in.
That's the briefing.…