Vue 3.5

Vue 3.5 substantially revised the reactivity internals, using a new dependency-tracking approach intended to reduce memory use, improve tracking for large reactive arrays, and address an SSR-related computed-value memory issue. It added numeric depth limits for deep watchers, so a watcher can traverse only a bounded number of nested levels. Watcher cleanup can now be registered with onWatcherCleanup() during the synchronous portion of a watcher or watchEffect callback. In single-file components, destructured defineProps() values are now compiler-transformed into reactive prop accesses, and JavaScript default-value syntax can provide prop defaults. The cycle also added useTemplateRef() for typed template refs, deferred Teleport support, controlled hydration mismatch allowances through data-allow-mismatch, and built-in lazy-hydration strategies for async components.

Vue 3.5 remains a supported line, so remaining on it does not by itself require an urgent migration. The practical trade-off is that the application will not receive improvements, fixes, or APIs introduced by later supported Vue releases, and related tooling or component libraries may eventually raise their minimum Vue baseline. Teams that rely on deep watchers, SSR, large reactive collections, or compiler behavior should also recognize that moving between Vue minors can expose assumptions that were previously hidden by runtime or compiler behavior. In particular, reactive props destructuring is scoped to the compiled component context; passing a destructured prop directly to code that expects a reactive source may require a getter or another explicit reactive wrapper. Delaying routine minor-version upgrades increases the amount of application, build-tool, test, and dependency change that must be validated together later.

Keep Vue, the matching compiler package, and Vue language tooling on their latest compatible 3.5 patch levels while the team plans its next supported-minor upgrade. Inventory dependencies that declare Vue peer requirements, including component libraries, SSR integrations, test utilities, and plugins, then identify the highest Vue minor they support. Run the application’s unit, browser, type-checking, and SSR or hydration tests against the target version in a separate upgrade branch. Add focused tests for watcher cleanup timing, bounded deep-watch behavior, reactive props destructuring, Teleport behavior, and hydration warnings where those features are used. Upgrade the runtime and compiler together, review build and type-check output for compiler-transform changes, and deploy through the team’s normal staged rollout process with monitoring for client-side errors and hydration mismatches.