KIMJINWOO4KIMJINWOO4/vue-skills/skills/vue-upgrade/SKILL.md

vue-upgrade

Skill28 starsChanged 32 days agoMITView on GitHub

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.

In this repository16 other files it gives its agents.
- antfuSkill
- build-toolingSkill
- designSkill
- find-skillsSkill
- nuxtSkill
- vitepressSkill
- vue-a11ySkill
- vue-ciSkill
- vue-clean-componentsSkill
- vue-dataSkill
- vue-debugSkill
- vue-formsSkill
- vue-performanceSkill
- vue-reviewSkill
- vueSkill
- vue-uiSkill

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Inventory: Read package.json and the lockfile.
line 12
Very specific:
Do not upgrade to a pre-release (rc, beta, nightly) unless the user asks for it.
line 35
Very specific:
Keep the lockfile change in the same commit as the package.json change.
line 37
Distinctive:
If a peer dependency warning appears, resolve it.
line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

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

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.
Check the floors. Node, Vue and TypeScript minimums block upgrades more often than API changes do. The table in versions lists them.
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.
Read the guide for that package below, and apply the breaking changes before fixing anything else.
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

Upgrade	Guide
Vue 2 to Vue 3	vue-2-to-3
Vue 3.5 to 3.6 RC, Vapor Mode	vue-3.6
Pinia 3 to 4	pinia-4
Vue Router 4 to 5, unplugin-vue-router to core	router-v5 in the `vue` skill
VueUse 14 to 15	vueuse-15
Vite 7 to 8, 8.x minors	vite-8
Vitest 4 to 5	vitest-5
Nuxt 3 to 4, 4.5 and 4.6, getting ready for 5	nuxt
pnpm 11 to 12	pnpm-12
TypeScript 6 to 7, and why Vue projects keep TS 6 for vue-tsc	typescript-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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free