Vue.js: Custom Element Mount Order Fix
A single pull request addresses a timing bug in Vue's custom elements, ensuring nested async components mount in the correct ancestor-first order and don't mount at all if their host has already been disconnected.
Duration: PT1M59S
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-07-24T13:09:45Z
- Audio duration: PT1M59S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's July 24th, and today's briefing covers one focused but important fix in Vue core.
Pull request 15154, from edison1105, tackles a mounting order problem in custom elements. When custom elements are nested and resolve asynchronously, they can complete out of order — meaning a child element might try to mount before its parent has finished setting up. This PR closes issue 15153 by enforcing…
There's a second piece worth flagging here: the fix also guards against a related edge case. If a host element gets disconnected before its async descendant resolves, that descendant now correctly skips mounting altogether — rather than mounting into a shadow DOM that shouldn't be updated anymore. Mounting picks…
Why this matters: async custom elements are a pattern that's easy to get subtly wrong, because component setup and DOM lifecycle don't always resolve in the order you'd expect. Without this fix, developers using nested async custom elements could see children render before parents, or worse, mount into detached DOM…
The scope here stayed narrow — this is a targeted correctness fix in the custom element and API custom element areas, not a broader refactor. There isn't a…
Wha…
Nearby episodes from Vue.js
- Vapor Hydration and Attribute Fixes
- Vapor Mode's Suspense Boundary Problem
- Vapor Mode's Nuxt Reckoning
- Vapor Mode Hardens Its Edges
- Weekly Recap - Hydration Hardening and Reactivity Edge Cases
- Tightening Correctness Across Tooling and Runtime
- Type System Tightens Up, Resource Props Get Smarter
- Production Bugs Hiding in Plain Sight