Vue 3.5 Released: Reactive Props Destructure and SSR Improvements
Vue 3.5 stabilised reactive props destructure, refactored the reactivity system for 56% lower memory use, and added lazy hydration and a useId API for server-side rendering.
Historical Archive. This article documents an event from 2024 and is preserved with its original date for reference. It is not current news, and details may have changed since publication.
What happened
Vue 3.5, nicknamed Tengen Toppa Gurren Lagann, was released on September 1, 2024, according to the official Vue blog post by Evan You. It is a minor release with no breaking changes, combining internal performance work with several developer-facing features.
Reactivity and performance
Vue 3.5's reactivity system underwent another major refactor that improved performance and significantly reduced memory usage, by about 56%, with no behavioural changes. The refactor also resolved issues with stale computed values and hanging computeds during server-side rendering, and optimised reactivity tracking for large, deeply reactive arrays, making some operations up to ten times faster.
Reactive props destructure
The headline feature is that reactive props destructure was stabilised and enabled by default. Variables destructured from a defineProps call in script setup are now reactive, which notably simplifies declaring props with default values using JavaScript's native default-value syntax rather than the older withDefaults helper. Accessing a destructured variable is compiled into a property access on props so it is tracked on access.
SSR and other additions
Vue 3.5 brought long-requested server-side-rendering improvements: lazy hydration lets async components control when they hydrate through a strategy such as hydrate-on-visible, and a new useId API generates stable unique IDs across server and client to avoid hydration mismatches. The release also added useTemplateRef for obtaining template refs via runtime string IDs, a defer prop for Teleport, and an onWatcherCleanup API for registering watcher cleanup callbacks.
Why it mattered
Vue 3.5 delivered meaningful memory and performance gains for free while stabilising an ergonomic way to declare props. The SSR improvements, especially lazy hydration and useId, addressed real pain points for framework authors like Nuxt, reinforcing Vue's steady, backwards-compatible evolution.
Related on Skillo
See also: Vue 3.4 and its 2x faster parser.
Sources
Published date reflects the original event date (2024-09-01). This article is original Skillo editorial written from the sources above; facts were verified in September 2026.
Written by
Skillo Staff
0 Comments
Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.