$ the-wire · showcase
Server renderer surfaces async setup errors, VitePress prefetch goes network-aware
By RepoJournal · Filed · About Vue.js · Composed from the cited sources · methodology
3 people shipped this
Vue's server renderer now reports failures that previously vanished when another part of the page was still rendering, and VitePress's link prefetching stops firing when the browser is offline.
fix(server-renderer): propagate async setup errors vuejs/core
Async setup and render failures are now reported to the caller even while other parts of the page are still rendering, and rejected server-prefetch promises no longer disrupt the render. Watchers are stopped after rendering completes or fails, so SSR error paths stop swallowing the exception: "Server rendering now reports asynchronous setup and rendering failures to the caller, even when anothe...
fix(client): Move the online status check inside IntersectionObserver callback vuejs/vitepress
The online status check moves inside the IntersectionObserver callback, because guarding only the observer's creation still left prefetch links being generated once the observer existed. userquin notes the connection and save-data checks should move inside the observer too, since they are not reactive.
fix(client): make link prefetching reactive to network and consistent with the router vuejs/vitepress
Link prefetching becomes reactive to network conditions and consistent with the router, following up on the earlier offline guard.
fix(client): don't create prefetch link when offline (#5534) vuejs/vitepress
Companion change that stops prefetch links from being created at all when the browser is offline.
chore(deps): update all non-major dependencies vuejs/core
The rest of the day was Renovate: non-major dependency bumps, lint tooling (eslint ^10.10.0 to ^10.12.0), build tooling (@swc/core ^1.16.2 to ^1.16.18), and monaco-editor ^0.56.0 to ^0.57.0 in the playground. Routine, with nothing to act on.
