nuxt
4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed
Upgrading nuxt From 2.13.2 to 2.13.3
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 0
- changes to make
- 0
- advisories fixed
- 0
- new
- 7
- fixes
Security
3 advisories still affect 2.13.3
- 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
- Fixed
vue-app: Check plugin key on
Vue.prototypeinstead ofVue - Fixed
vue-app: Sanitize path with trailing slash in
getLocation(resolves #6744) - Fixed
vue-app: Handle layout on client error (resolves #7567)
- Fixed
vue-app: Don't fetch payload on first spa fallback render (resolves #7648)
- Fixed
webpack: Modern build should wait for legacy assets (resolves #7562, resolves #7628)
- Fixed
webpack: Use compact name for concatenated modules (resolves #7625)
- Fixed
cli: Handle nuxt static command 👀
- Fixed
1 other line we could not sort, mostly version bumps
- 2.13.3
general: Import types for
@nuxt/telemetryand@nuxt/components
3 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.