Modernize Vue.js
Operational guides for Vue.js: the Vue 3 upgrade hub, the Vue 2 to Vue 3 migration path, Options API to Composition API modernization, and fixing Vue 3 migration errors.
Last verified · Updated May 22, 2026
Vue 2 reached end of life in December 2023 and no longer receives security patches. This hub links the Vue 3 upgrade path, the Options API to Composition API modernization, and the workflow for diagnosing the errors those changes surface.
What this covers
Start at the Vue 3 upgrade hub for the full breaking-change picture, then follow the Vue 2 to Vue 3 path for the version upgrade itself. Once you are on Vue 3, the Options API to Composition API guide covers the optional pattern modernization. Each page includes a repo-inspection prompt, step-by-step migration, a test plan, and rollback guidance.
Version timeline
- 3.x — current, active (released 2020-09-18)
- 2.x — eol (released 2016-09-30 · EOL 2023-12-31)
Vue migration paths
- Migrate Vue Options API to Composition API — Migration
- Upgrade to Vue 3 — Upgrade hub
- Upgrade to Vue 3 — Version path
- Vue 2 to Vue 3 Migration Guide — Version path
- Fix Vue 3 Migration Errors — Workflow
Frequently asked questions
Which Vue version should I target?
Target Vue 3 — it is the current and only supported line, with 3.5.x as the latest stable release. Vue 2 reached end of life on 2023-12-31. Vue 3.6 (which adds the opt-in Vapor Mode compilation strategy) is in beta as of mid-2026, so build on 3.5.x today; 3.6 is a backward-compatible minor when it ships. Use the @vue/compat migration build to move from Vue 2 to Vue 3 incrementally. Adopting the Composition API is a separate, optional modernization you can do after the upgrade.