nuxt
4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed
Upgrading nuxt From 3.13.2 to 3.14.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
Security
19 advisories still affect 3.14.0
- Nuxt: Unauthorized Component Instantiation via Server Island Propsmoderate · GHSA-48hr-524c-v5w3
- Nuxt: Route rules are matched against the raw request path, so a percent-encoded segment can bypass `appMiddleware` on dynamic and catch-all routesmoderate · GHSA-6gq8-jgmh-3ffp
- Nuxt: Reflected XSS in `<NuxtLink>` via unsanitised `javascript:` or `data:` URLmoderate · GHSA-934w-87qh-qr26
No published version clears them all yet.
Release by release
- New
Previously, if you had a component like
~/components/App/Header.vuethis would be visible in your devtools as<Header>. From v4 we ensure this is<AppHeader>, but it's opt-in to avoid breaking any manual<KeepAlive>you might have implemented. (#28745). - New
Nuxt scans page metadata from your files, before calling
pages:extend. But this has led to some confusing behaviour, as pages added at this point do not end up having their page metadata respected. So we now do not scan metadata before callingpages:extend. Instead, we have a newpages:resolvedhook, which is called afterpages:extend, after all pages have been augmented with their metadata. I'd recommend opting into this by settingexperimental.scanPageMetatoafter-resolve, as it solves a number of bugs. - New
deps: Upgrade to latest version of jiti
- New
kit,nuxt,vite,webpack: Reimplement cjs utils using
jiti
- New
3 other lines we could not sort, mostly version bumps
- 3.14.0
auto-imported directives from modules
- 3.14.0
'isolated' page renders
- 3.14.0
Delayed hydration
41 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.