nuxt
4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed
4.6.4 is the newest release of 4.x.
In short
25 breaking28 new3 faster31 fixed4 changed50 internal
- Breaking
This is a stability-focused major release, introducing a few thoughtful breaking changes in order to improve development experience.
- Breaking
Although any major release brings breaking changes, one of our main aims for this release is to ensure that the upgrade path is as smooth as possible.
- Breaking
nuxt: ⚠️ Don't call
render:htmlfor server islands - Breaking
schema,vite: ⚠️ Do not allow configuring vite dev bundler
- Breaking
schema: ⚠️ Default to
compatibilityVersion: 4 - Breaking
nuxt: ⚠️ Emit absolute paths in
builder:watchhook - Breaking
nuxt: ⚠️ Improve default
asyncDatavalue behaviour - Breaking
nuxt: ⚠️ Remove old experimental options
Security
21 advisories affect 4.0.0; 4.6.2 fixes the others
- ModerateNuxt exposes the message and data of unhandled errors thrown during server renderingGHSA-96x6-fvhx-49hg · 16 Nov 2026No fix yet
- ModerateNuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routesGHSA-f3x9-2chm-73c8 · 16 Nov 2026No fix yet
- ModerateNuxt: Server-side route rules (`redirect`, `headers`, `proxy`, `ssr`) are skipped for case-variant paths when routing is case-insensitiveGHSA-vjh5-4x84-xrqp · 22 Oct 2026No fix yet
- LowNuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)GHSA-hf59-9xwc-2g4p · 16 Nov 2026No fix yet
- HighNuxt: Unauthenticated CPU exhaustion parsing and hashing the Nuxt island endpoint body before hash validationGHSA-9pgf-384g-p7mv · 5 Aug 2026Fixed in 4.5.1
16 more
- HighNuxt: Server-Side Remote Code Execution via Runtime Template Injection in Nuxt Server Island PropsGHSA-9473-5f9j-94wq · 5 Aug 2026Fixed in 4.5.1
- HighNuxt: Unauthenticated out-of-memory crash via unbounded v-for expansion in island renderingGHSA-hxcr-hm88-mpq6 · 5 Aug 2026Fixed in 4.5.1
- HighNuxt: Route-rule middleware bypass via case-sensitivity mismatch between vue-router and the routeRules matcherGHSA-mm7m-92g8-7m47 · 16 Jun 2026Fixed in 4.4.7
- ModerateNuxt server islands render `useHeadSafe` input without sanitisationGHSA-xfq5-w38q-pc2x · 22 Oct 2026Fixed in 4.6.2
- ModerateNuxt: Route rules are matched against the raw request path, so a percent-encoded segment can bypass `appMiddleware` on dynamic and catch-all routesGHSA-6gq8-jgmh-3ffp · 22 Oct 2026Fixed in 4.4.4
- ModerateNuxt: Unauthorized Component Instantiation via Server Island PropsGHSA-48hr-524c-v5w3 · 5 Aug 2026Fixed in 4.5.1
- ModerateNuxt: Reflected XSS in `<NuxtLink>` via unsanitised `javascript:` or `data:` URLGHSA-934w-87qh-qr26 · 16 Jun 2026Fixed in 4.4.7
- ModerateNuxt dev server vite-node IPC socket is world-connectable on LinuxGHSA-534h-c3cw-v3h9 · 16 Jun 2026Fixed in 4.4.7
- ModerateNuxt: URL-handling weaknesses in `navigateTo` and `reloadNuxtApp`: SSR open redirect, client-side script execution via the `open` option, and protocol-relative bypass in `reloadNuxtApp`GHSA-c9cv-mq2m-ppp3 · 16 Jun 2026Fixed in 4.4.7
- ModerateNuxt's route middleware is not enforced when rendering `.server.vue` pages via `/__nuxt_island/page_*`GHSA-hg3f-28rg-4jxj · 29 May 2026Fixed in 4.4.6
- ModerateNuxt: Reflected XSS in `navigateTo()` external redirectGHSA-fx6j-w5w5-h468 · 19 May 2026Fixed in 4.4.6
- LowNuxt: Incomplete fix for GHSA-934w-87qh-qr26: a `javascript:` URL prefixed with an ASCII control character executes from `<NuxtLink>` when `pages` is disabledGHSA-jjm6-p2m9-9w4x · 22 Oct 2026Fixed in 4.6.0
- LowCross-site scripting via <NoScript> slot content in Nuxt's head componentsGHSA-m3q2-p4fw-w38m · 16 Jun 2026Fixed in 4.4.7
- LowNuxt: Dev server discloses project absolute path and persistent workspace UUID via `/.well-known/appspecific/com.chrome.devtools.json`GHSA-rq7w-g337-39qq · 15 Jun 2026Fixed in 4.4.7
- LowNuxt: `__nuxt_island` endpoint does not bind responses to request props, enabling shared-cache poisoningGHSA-g8wj-3cr3-6w7v · 19 May 2026Fixed in 4.4.6
- LowNuxt has Client-Side Path Traversal in Nuxt Island Payload RevivalGHSA-p6jq-8vc4-79f6 · 17 Sep 2025Fixed in 4.1.0
Release note
Nuxt 4.0 is here! 🎉
After a year of real-world testing, we're excited to announce the official release of Nuxt 4. This is a stability-focused major release, introducing a few thoughtful breaking changes in order to improve development experience.
If you've been following along, you'll recognize many of these features and changes — and if you're new to them, we hope you'll welcome them.
What's new?
Nuxt 4 is all about making your development experience smoother:
Cleaner project organization with the new
app/directory structureSmarter data fetching - we've taken the opportunity to address some inconsistencies and improve performance with the data layer
Better TypeScript support with project-based separation between the different contexts in your project - app code, server code,
shared/folder, and configurationFaster CLI and development with adoption of internal sockets and a faster CLI
Why these features in particular? Mostly because these kind of improvements have required making changes that are technically breaking.
In general, we aim for a hype-free approach to releases. Rather than save up features for a big release, we've been shipping improvements in Nuxt 3 minor releases.
We've also spent a lot of time figuring out how to implement these changes in a backwards-compatible way, and I hope that means that most Nuxt 3 projects can upgrade with a minimum of effort.
I'd advise reading through the upgrade guide before you start, to understand what areas of your app might be affected.
New project structure
The biggest visible change is how projects are organized. Your application code now lives in an app/ directory by default:
my-nuxt-app/ ├─ app/ │ ├─ components/ │ ├─ pages/ │ ├─ layouts/ │ └─ app.vue ├─ public/ ├─ shared/ ├─ server/ └─ nuxt.config.ts
This helps keep your code separate from node_modules/ and .git/, which makes file watchers faster (especially on Windows and Linux). It also gives your IDE better context about whether you're working with client or server code.
Tip
Don't want to migrate? That's totally fine! Nuxt will detect your existing structure and keep working exactly as before.
Updated UI templates
Nuxt’s starter templates have an all new look, with improved accessibility, default titles, and template polish (#27843).
Smarter data fetching
We've made useAsyncData and useFetch work better. Multiple components using the same key now share their data automatically. There's also automatic cleanup when components unmount, and you can use reactive keys to refetch data when needed. Plus, we've given you more control over when cached data gets used.
Some of these features have already been made available in Nuxt v3 minor releases, because we've been rolling this out gradually. Nuxt v4 brings different defaults, and we expect to continue to work on this data layer in the days to come.
Better TypeScript experience
Nuxt now creates separate TypeScript projects for your app code, server code, shared/ folder, and builder code. This should mean better autocompletion, more accurate type inference and fewer confusing errors when you're working in different contexts.
Tip
With Nuxt 4, you will only need one tsconfig.json file in your project root!
This is probably the single issue that is most likely to cause surprises when upgrading, but it should also make your TypeScript experience much smoother in the long run. Please report any issues you encounter. 🙏
Faster CLI and development
In parallel with the release of v4, we've been working on speeding up @nuxt/cli.
Faster cold starts - Development server startup is noticeably faster
Node.js compile cache - Automatic reuse of the v8 compile cache
Native file watching - Uses
fs.watchAPIs for fewer system resourcesSocket-based communication - The CLI and Vite dev server now communicate via internal sockets instead of network ports, reducing overhead — particularly on Windows
These improvements combined can make a really noticeable difference in your day-to-day development experience, and we have more planned.
How to upgrade
Although any major release brings breaking changes, one of our main aims for this release is to ensure that the upgrade path is as smooth as possible. Most of the breaking changes have been testable with a compatibility flag for over a year.
Most projects should upgrade smoothly, but there are a few things to be aware of:
Nuxt 2 compatibility has been removed from
@nuxt/kit. (This will particularly affect module authors.)Some legacy utilities and deprecated features have been cleaned up.
The new TypeScript setup might surface some type issues that were hidden before.
A few modules might need further updates for full Nuxt 4 compatibility.
Don't worry though — for most breaking changes, there are configuration options to revert to the old behavior while you adjust.
1. Update Nuxt
Our recommendation for upgrading is to run:
npx nuxt upgrade --dedupe
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
2. Optional: use migration tools
We’ve also partnered with Codemod to automate many, though not all, migration steps:
npx codemod@latest nuxt/4/migration-recipe
3. Test and adjust
Run your tests, check that everything builds correctly, and fix any issues that come up. The upgrade guide has detailed migration steps for specific scenarios.
We'd recommend reading through it in full before starting your upgrade, to understand what areas of your app might be affected.
What's next?
We're planning quick patch releases to address any issues that come up. Nuxt 3 will continue to receive maintenance updates (both bug fixes and backports of features from Nuxt 4) until the end of January 2026, so there's no rush if you need time to migrate.
Looking ahead, we plan to release Nuxt 5 on the sooner side, which will bring Nitro v3 and h3 v2 for even better performance, as well as adopting the Vite Environment API for an improved (and faster!) development experience. And there's a lot more in the works too!
And, quite apart from major releases, we have a lot of exciting features planned to make their way into Nuxt 3.x and 4.x release branches, including support for SSR streaming (#4753), a first-party accessibility module (#23255), built-in fetch caching strategies (#26017), more strongly typed fetch calls (landing in Nitro v3), dynamic route discovery (#32196), multi-app support (#21635) and more.
Changelog
Enhancements
ui-templates: Update template branding for v4
deps: Upgrade to latest versions of c12, jiti and unbuild
kit: Reimplement cjs utils using
mllynuxt: Generate basic jsdoc for module config entry
schema: Split dev/prod build directories
nuxt: Cache vue app build outputs
nuxt: Add integration with chrome devtools workspaces
kit: Support single import in
addServerImportsnuxt: Add
onWatcherCleanupto imports presetskit,nuxt,schema: Separate ts projects for node/app/nitro
nuxt: Support lazy hydration macros
nuxt: Export
<NuxtTime>prop typesnuxt: Add route announcer to default app.vue
nuxt: Expose page routes to nitro for o11y
Performance
nuxt: ⚠️ Don't call
render:htmlfor server islandsvite: Don't write stub manifest for legacy bundler
kit: Update env expansion regex to match nitro
vite: Communicate with vite-node via internal socket
Fixes
schema,vite: ⚠️ Do not allow configuring vite dev bundler
schema: ⚠️ Default to
compatibilityVersion: 4nuxt: ⚠️ Emit absolute paths in
builder:watchhooknuxt: ⚠️ Improve default
asyncDatavalue behaviournuxt: ⚠️ Remove old experimental options
kit: ⚠️ Support loading nuxt 4 and drop support for <=2
nuxt: ⚠️ Remove
__NUXT__after hydrationui-templates: Add default title back
kit: ⚠️ Drop support for building nuxt 2 projects
nuxt: ⚠️ Bump internal majorVersion to
4kit: Mark
resolvePathutils as synckit: Revert change to
tryResolveModulekit: Add back
requireModuleandtryRequireModulenuxt: Hide unhandled error messages in prod
nuxt: Add
useScriptCrispscripts stubnuxt: ⚠️ Remove unused
globalNamepropertynuxt: Use static import for
updateAppConfigin HMRvite: Write dev manifest when
ssr: falsekit,nuxt,schema: ⚠️ Remove other support for nuxt2/bridge
webpack: Only insert dynamic require plugin when building
nuxt: Guard
windowaccessnuxt: Remove unneeded subpath import
webpack: Handle new webpack chunk format
kit: ⚠️ Do not check compatibility for nuxt version < 2.13
ui-templates: Fix examples link and add bluesky
vite: Use
resolveIdfromvite-nodeto resolve depsnuxt: Import
isEqualfrom mainohashexportvite: Don't set
output.preserveModulesnuxt: Ignore
#app-manifestimport in dev modenuxt: Ensure layer array-type config is merged in order
schema: Turn off
purgeCachedDatauntil v4schema: Re-enable
purgeCachedDataby defaultwebpack: Expand dynamic require regexp to match new pattern
nuxt: Add back missing reset of
.executenuxt,schema: ⚠️ Remove support for
compatibilityVersion: 3kit,nuxt,schema,vite: ⚠️ Remove support for some deprecated options
nuxt: ⚠️ Don't rerun asyncdata w/ existing data in
useAsyncDatanuxt: Scan nitro handlers before writing types
nuxt: Force asyncData
errorValue/valueto be undefinednuxt: ⚠️ Remove public and assets aliases
webpack: Update dynamic require pattern
schema: ⚠️ Remove top level generate option
ui-templates: Add aria tag on Nuxt logo
nuxt: Augment runtime config in server context
kit: Do not skip layer with defined
srcDirdeps: Upgrade to rc version of
@nuxt/clikit: Ensure legacy
tsConfigdoesn't exclude too many typeskit: Ensure types of module entrypoints are in node project
kit: Add layer
app/andserver/folders into tsconfigsschema: Disable changing compat version
nuxt: Allow modules to add to
typescript.hoistnuxt: Include shared declarations in
tsconfig.server.jsonnuxt: Retain old data when computed key changes
nuxt: ⚠️ Bump
compatibilityDateto2025-07-15nuxt: Only use
scrollBehaviorTypefor hash scrolling
CI
Breaking Changes
- Breaking
nuxt: ⚠️ Don't call
render:htmlfor server islands - Breaking
schema,vite: ⚠️ Do not allow configuring vite dev bundler
- Breaking
schema: ⚠️ Default to
compatibilityVersion: 4 - Breaking
nuxt: ⚠️ Emit absolute paths in
builder:watchhook - Breaking
nuxt: ⚠️ Improve default
asyncDatavalue behaviour - Breaking
nuxt: ⚠️ Remove old experimental options
- Breaking
kit: ⚠️ Support loading nuxt 4 and drop support for <=2
- Breaking
nuxt: ⚠️ Remove
__NUXT__after hydration - Breaking
kit: ⚠️ Drop support for building nuxt 2 projects
- Breaking
nuxt: ⚠️ Bump internal majorVersion to
4 - Breaking
nuxt: ⚠️ Remove unused
globalNameproperty - Breaking
kit,nuxt,schema: ⚠️ Remove other support for nuxt2/bridge
- Breaking
kit: ⚠️ Do not check compatibility for nuxt version < 2.13
- Breaking
nuxt,schema: ⚠️ Remove support for
compatibilityVersion: 3 - Breaking
kit,nuxt,schema,vite: ⚠️ Remove support for some deprecated options
- Breaking
nuxt: ⚠️ Don't rerun asyncdata w/ existing data in
useAsyncData - Breaking
nuxt: ⚠️ Remove public and assets aliases
- Breaking
schema: ⚠️ Remove top level generate option
- Breaking
nuxt: ⚠️ Bump
compatibilityDateto2025-07-15 - Breaking
kit,nuxt: ⚠️ Drop nuxt 2 + ejs template compile support
- Breaking
nuxt: ⚠️ Move
#app/components/layout->#app/components/nuxt-layout - Breaking
kit,nuxt,vite,webpack: ⚠️ Remove legacy require utils
- Breaking
schema: ⚠️ Remove config.schema.json export + defaults
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.