nuxt
4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed
Upgrading nuxt From 2.13.1 to 2.13.2
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 1
- change to make
- 0
- advisories fixed
- 0
- new
- 6
- fixes
Before you upgrade
Tick each one off as you go- Breaking2.13.2
Security
3 advisories still affect 2.13.2
- 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
core: Avoid breaking change for duplicate modules (resolves #7605)
- Fixed
webpack: Explicitly pass
outputFileSystemtowebpackDevMiddleware(resolves nuxt/typescript#145) - Fixed
webpack: Chunk name normalization for catch-all pages and windows
- Fixed
cli: Listen to a random port for export and generate (resolves #7597)
- Fixed
vue-app: Remove hash from payload path
- Fixed
vue-app: Fix wrong layout when redirecting from error page (resolves #7567)
- Fixed
utils: Flat routes if child routes have absolute paths
- Breaking
2 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.