nuxt
4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed
Upgrading nuxt From 2.15.8 to 2.16.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 5
- changes to make
- 0
- advisories fixed
- 13
- new
- 28
- fixes
Start here
Before you upgrade
Tick each one off as you go- Breaking2.16.0
- Breaking2.16.0
- Breaking2.16.0
- Breaking2.16.0
- Breaking2.16.0
Security
3 advisories still affect 2.16.0
- Nuxt: Incomplete fix for GHSA-934w-87qh-qr26: a `javascript:` URL prefixed with an ASCII control character executes from `<NuxtLink>` when `pages` is disabledlow · GHSA-jjm6-p2m9-9w4x
- Cross-site scripting via <NoScript> slot content in Nuxt's head componentslow · GHSA-m3q2-p4fw-w38m
- nuxt vulnerable to Cross-site Scripting in navigateTo if used after SSRmoderate · GHSA-vf6r-87q4-2vjf
Upgrading to 4.6.0 clears them.
Release by release
- Breaking
Upgrade to PostCSS 8
- Breaking
In this PR we only support Node 14+. This is mostly an issue for dependencies, which we need to keep updated for security reasons. Going forward until its own EOL, Nuxt 2 will only officially support Node versions that have not reached their EOL.
- Breaking
Dependency upgrades. A number of dependencies have dropped support for earlier node versions.
dotenvhas changed how it parses.envfiles in a number of edge cases.globnow requires/instead of\on windows machines. There may also be other changes that affect your usage, so please do upgrade with care. - Breaking
Vue 2.7 upgrade. Although you can use Vue 2.7 with any release of Nuxt 2, 2.16.0 for the first time includes it as a dependency, which means that you may well encounter some issues associated with upgrading Vue 2.6 -> Vue 2.7.
- Breaking
42 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.