Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Other skills

vue-upgrade

Upgrade Vue projects across major versions. Breaking changes and step-by-step migration for Vue 2 to 3, Vue 3.6 and Vapor, Pinia 4, Vue Router 5, VueUse 15, Vite 8, Vitest 5, Nuxt 4.x and Nuxt 5 prep, pnpm 12 and TypeScript 7 with vue-tsc. Use when bumping dependencies, reading a changelog, fixing errors after an upgrade, or planning a migration.

KIMJINWOO4 · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add KIMJINWOO4/vue-skills --skill vue-upgrade

About this skill


name: vue-upgrade description: Upgrade Vue projects across major versions. Breaking changes and step-by-step migration for Vue 2 to 3, Vue 3.6 and Vapor, Pinia 4, Vue Router 5, VueUse 15, Vite 8, Vitest 5, Nuxt 4.x and Nuxt 5 prep, pnpm 12 and TypeScript 7 with vue-tsc. Use when bumping dependencies, reading a changelog, fixing errors after an upgrade, or planning a migration.

Vue Upgrades

Versions and floors were checked against npm and release notes on 2026-10-15. Start with versions to see what is current and what each package needs.

Process

  1. Inventory. Read package.json and the lockfile. Write down the current and target major for each package. nlx fast-npm-meta version <pkg> or npm view <pkg> dist-tags shows what is published.
  2. Check the floors. Node, Vue and TypeScript minimums block upgrades more often than API changes do. The table in versions lists them.
  3. One major at a time. Upgrade a single package (plus its companion packages), run the checks, commit, then move on. Suggested order: package manager, Node, TypeScript, Vite, Vitest, Vue, Router and Pinia, VueUse, then Nuxt.
  4. Read the guide for that package below, and apply the breaking changes before fixing anything else.
  5. Verify. Type-check, run unit and end-to-end tests, build for production, and click through the main flows. A clean npm install is not proof.

Guides

UpgradeGuide
Vue 2 to Vue 3vue-2-to-3
Vue 3.5 to 3.6 RC, Vapor Modevue-3.6
Pinia 3 to 4pinia-4
Vue Router 4 to 5, unplugin-vue-router to corerouter-v5 in the vue skill
VueUse 14 to 15vueuse-15
Vite 7 to 8, 8.x minorsvite-8
Vitest 4 to 5vitest-5
Nuxt 3 to 4, 4.5 and 4.6, getting ready for 5nuxt
pnpm 11 to 12pnpm-12
TypeScript 6 to 7, and why Vue projects keep TS 6 for vue-tsctypescript-7 in the build-tooling skill

Rules

  • Do not upgrade to a pre-release (rc, beta, nightly) unless the user asks for it.
  • Codemods first, hand edits second. Use the official migration tooling where it exists (npx nuxt upgrade, @vue/compat), and review its diff.
  • Keep the lockfile change in the same commit as the package.json change.
  • If a peer dependency warning appears, resolve it. Pinia 4 and Vitest 5 both turned optional packages into required peers.