@nuxt/rspack-builder
4.6.4 · 2 Nov 2026MIT590 / weekRepositoryHomepagenpmAtom feed
67 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 4.x · latest line
4.6.4
2 Nov 2026Error details in production. When a page fails to render on the server, the error page and the payload now only carry message and data of errors you create with
createError. Everything else is stripped.Dev server
Hostchecks. Webpack and rspack dev servers now reject requests with an unexpectedHostheader, as Vite already does. If you use a custom hostname or tunnel, you'll need to add it to the newdevServer.allowedHostsoption.workspaceDirdetection. WhenworkspaceDirisn't set, Nuxt now only widens it pastrootDirto an explicit workspace root or the closest git repository.
4.6.4 is a security release. It fixes eight advisories in Nuxt and pulls in
nitropack2.13.6, which fixes three more in Nitro. We recommend upgrading as soon as you can.Behaviour changes
These probably won't affect most apps, but it's worth flagging anyway:
Error details in production. When a page fails to render on the server, the error page and the payload now only carry message and data of errors you create with
createError. Everything else is stripped.Dev server
Hostchecks. Webpack and rspack dev servers now reject requests with an unexpectedHostheader, as Vite already does. If you use a custom hostname or tunnel, you'll need to add it to the newdevServer.allowedHostsoption.workspaceDirdetection. WhenworkspaceDirisn't set, Nuxt now only widens it pastrootDirto an explicit workspace root or the closest git repository.Nitropack cached routes.
cache,swrandisrroute rules now only cacheGETandHEADrequests, and no longer store responses that set a cookie or sendCache-Control: privateorno-store. Wildcardproxyandredirectrules also reject requests whose resolved target would leave the rule's scope.Route rules and encoded slashes. Route rules now match paths that contain encoded slashes, so
/api%2Fadminis covered by a/api/**rule.
Changelog
Fixes
rspack,webpack: reject unexpected Host headers in dev middleware
nitro,vite: remove windows + virtual dev ssr css links after hydration
4.6.3
27 Oct 2026- Security
vite: do not read files named in client error reports (
63299e13c) - GHSA-x287-wcfc-q46c - Security
vite: deny dev server access to nitro dev output (
c7e204ec6) - GHSA-648h-gw55-m2g7 - Security
vite: deny serving generated app secret in dev (
16dfdc2a9) - GHSA-3xf4-9g3c-4h4w
v4.6.3 is the next patch release.
Changelog
Security fixes
- Security
vite: do not read files named in client error reports (
63299e13c) - GHSA-x287-wcfc-q46c - Security
vite: deny dev server access to nitro dev output (
c7e204ec6) - GHSA-648h-gw55-m2g7 - Security
vite: deny serving generated app secret in dev (
16dfdc2a9) - GHSA-3xf4-9g3c-4h4w - Security
nitro,nuxt: handle dot segments in request paths (
440250d97) - GHSA-9v7c-q64q-vv33 - Security
nuxt: apply redirect route rules to page islands (
b20372dbe) - GHSA-2fxj-c3j7-rr69
Performance
nitro,nuxt,rspack,webpack: bundle esm vue + reuse caches
Fixes
nuxt: remove purged entries from
_asyncDatarspack,webpack: register vue-loader plugin only once per config
deps: update nitropack to 2.13.5 + drop obsolete workarounds
4.6.2
16 Oct 20264.6.1
9 Oct 20264.6.0
5 Oct 2026v4.6.0 is the next minor release.
Some news
Nuxt CLI v4
Alongside the release of Nuxt v4.6, today also brings a new major release of the Nuxt CLI:
@nuxt/cliv4. It ships as a dependency ofnuxt, so you'll get it automatically when you upgrade.Most of what's new is in
nuxt dev:an interactive terminal UI, showing URLs, startup progress and keyboard shortcuts, with panels to dive into error logs, routes, network requests and more
the dev server gives you more info, such as why it reloaded or restarted, which
nuxt.configkeys changed, where the time went during a slow start or build, and how long each module took to set up
There's also a new
nuxt docs "<query>"search, andnuxt preview --takeovercan replace a running preview server. And in generalnuxt/cliis a lot smaller and starts a lot faster:v3.37 v4.0 @nuxt/cliinstall size13.1 MB 3.5 MB -73% @nuxt/clidependencies70 31 -56% nuxt dev: first paint330 ms 50 ms 6.6x faster nuxt dev: port bound338 ms 104 ms 3.2x faster nuxt dev: memory at rest (Linux)630 MB 440 MB -30% Although this is a major version, none of the changes should be breaking for Nuxt v4 users: we require Node.js v22.21+, v24.11+ or v26+, we drop
nuxt initand only supportnpm create nuxt@latest, and Nuxt 2 and@nuxt/bridgeare no longer supported.👉 Check out the full Nuxt CLI v4 release notes for everything that's changed.
A server-agnostic Nuxt
The biggest thing about this release is our move towards making Nuxt server-agnostic.
I feel that freedom of choice is very much a fundamental value of the web, and one that unites the whole Nuxt team.
You can use
pages/(with vue-router) or not. You can use Vite, webpack or Rspack to bundle your code. You can pick from dozens of providers to deploy to, pick any image or font provider, choose any database adapter. In every case, the framework is the same.The server side was different.
#appcomposables imported h3 types, server code imported fromh3andnitropack, and every module that touched the server was tied to whichever major version of those packages Nuxt happened to depend on.This has become particularly clear as we have been upgrading to new majors of h3 and nitro, which ship breaking changes with a cascading effect throughout the whole ecosystem.
👉 This release changes that.
Alongside explicitly defining our public API in
nuxt/kit(which now does not refer to external packages), Nuxt now specifies our own types for the request event, route rules and typed$fetch, and we expose an import surface (nuxt/server) for the server utilities that will be needed by most apps.This is the culmination of work we started almost a year ago, making it possible to use any server builder with Nuxt, not just Nitro (#33462).
Of course, under the hood,
nuxt/serveris still powered by Nitro by default - though we are also announcing a second, experimental implementation,@nuxt/vite-server, which allows pure-Vite server builds using the Vite Environment API.Important
We believe that Nitro is still the right choice for almost everyone.
🌟 We see a number of key benefits for
nuxt/server.it smooths the upgrade to Nuxt 5, which moves to Nitro v3 and h3 v2. Server code written against
nuxt/serveron 4.6 runs unchanged there, so a module can ship one file for both.it decouples Nuxt from the Nitro release cycle. Because we 'own' the API, we can adapt to breaking changes in Nitro or h3 without requiring a future major - and we can release Nuxt majors without having to wait for upstream releases.
it makes Nuxt's code more maintainable. It helps us preserve the separation of concerns between our API -
/appand/server- and the bundler + server that you ultimately want to build your app.
... and there are a number of other benefits too, from a single type surface to being able to iterate more quickly on features.
Finally, I want to say a special thank-you to @pi0, whose relentless focus on server agnosticism and work on h3, Nitro and web-standard server primitives over the last few years is what makes a portable
RequestEventpossible at all. Thank you, Pooya. ❤️Almost every feature in this release is already in the Nuxt 5 branch, and most of the remaining Nuxt 5 defaults can be tested today with
future.compatibilityVersion: 5(more details below!).Tip
Nuxt 3 reached end-of-life on July 31, 2026, so there is no 3.x release alongside this one. If you're still on v3, the upgrade guide is waiting for you.
Highlights
🤷 If you've read this far I'm afraid I have bad news for you: there's a lot more still to say! Nuxt 4.6 is one of our biggest minor releases, with over 420 commits since v4.5.2.
... so, you might want to grab a coffee! ☕️
nuxt/serverIt has been asked for for a long time, and it now exists (#36275)!
nuxt/serveris a new import source for server code: handlers, middleware and utilities - a complement tonuxt/app. Wherenuxt/appis for the part of your application that also runs in the browser,nuxt/serveris for the part that only runs on the server.import { defineEventHandler, getQuery } from 'nuxt/server' export default defineEventHandler((event) => { const { name } = getQuery<{ name?: string }>(event) return { message: `Hello, ${name ?? 'world'}!` } })The utilities use web standards and are typed against a portable
RequestEvent:event.req // Request event.url // URL event.res // { status, statusText, headers } event.res.headers // Headers event.context // per-request contextUnder
@nuxt/nitro-serverthey are backed by Nitro and h3, but you never import from either.So the same handler runs under Nitro v2, Nitro v3 or
@nuxt/vite-server, and a module that imports fromnuxt/serverdoesn't need a peer dependency onh3ornitropack.We think this will make a big difference in smoothing out the upgrade to Nuxt v5 and Nitro v3.
There is a typing benefit too. We no longer hoist h3 or Nitro types into your app to type
useRequestEvent,$fetchor route rules, which removes a source of type conflicts when versions differ (#36212, #36214, #36293).The surface is small, and covers what published modules and user code typically need:
defineEventHandler,createError/isNuxtError, request URL, headers, query, body (plain and validated with any Standard Schema library or a function), cookies, redirects, response status,getRouterParam(s),getRequestIP,handleCors,getRouteRules,useRuntimeConfig,useAppConfigand sessions.import { defineEventHandler, readValidatedBody } from 'nuxt/server' import { z } from 'zod' export default defineEventHandler(async (event) => { const user = await readValidatedBody(event, z.object({ name: z.string() })) return { created: user.name } })We encourage you to use web APIs (
event.req.headers, for example), or raise an issue if there's functionality you're missing fromnuxt/server🙏If you do need to step outside
nuxt/serverfor a particular handler, don't worry! Nothing has been taken away: importdefineEventHandlerand the helpers you need fromh3ornitropack/runtimeas before, and that handler works exactly as it did on Nuxt 4.5.import { defineEventHandler, readMultipartFormData } from 'h3' export default defineEventHandler(async (event) => { const parts = await readMultipartFormData(event) return { received: parts?.length ?? 0 } })Important
On Nuxt 4, the auto-imported
defineEventHandler,getQuery,readBodyand the rest are still h3's own helpers, which take a different shape of event. Import fromnuxt/serverexplicitly, includingdefineEventHandlerto use the new server runtime. If you mix the two, you'll see aNUXT_E8012error which should tell you which import to change.A few helpers also behave differently from their h3 v1 namesakes:
sendRedirectreturns the response rather than sending it,createErrortakesstatusandstatusText, and response headers are set throughevent.res.headers. The upgrade guide has a table of the differences.Nothing in this release requires a migration. But if you have server code you'd like to make portable ahead of Nuxt 5, this is the best way.
👉 Read the server imports guide.
appSecretand sessionsNuxt now has a root application secret:
runtimeConfig.appSecret, set withNUXT_APP_SECRET(#35874, thanks to @onmax). Modules and server features derive purpose-specific secrets from it withderiveSecret(purpose), soNUXT_APP_SECRETis the only secret you need to configure.openssl rand -base64 32
In development Nuxt generates and persists one if none is configured (and warns the first time a derived secret is used). Builds never generate one.
The first thing to use it is a set of session helpers in
nuxt/server(#36358). Sessions are sealed into a cookie with iron, so there's no server-side storage to configure:import { defineEventHandler, useSession } from 'nuxt/server' export default defineEventHandler(async (event) => { const session = await useSession<{ visits: number }>(event) await session.update(data => ({ visits: (data.visits ?? 0) + 1 })) return { visits: session.data.visits } })Note
As a reminder, runtime config keys prefixed with
app(runtimeConfig.app,runtimeConfig.appSecret) are reserved for Nuxt.Typed
$fetch, rebuilt$fetchanduseFetchhave been typed from your server routes for a long time. But the types were derived from Nitro'sInternalApiinterface, and past a few hundred routes they hit TypeScript's instantiation limit with the familiarTS2589: Type instantiation is excessively deep and possibly infinite.We've rebuilt typed fetch on top of
fetchdts(#36238). Nuxt compiles your server routes into a route tree with an exact-match table for static paths and accessors specialised to your route set. Resolution cost now scales with call sites, not with route count:routes before after 100 1,397,361 instantiations / 0.77s 51,558 / 0.26s 300 5,774,425 / 3.49s ( TS2589)51,558 / 0.16s 1000 12,831,467 / 7.44s ( TS2589)51,558 / 0.20s 3000 (200 call sites) 71,875,148 / 53.63s ( TS2589)101,678 / 0.62s Peak memory for the same runs dropped from 946 MB to 140 MB. 🔥
Plus, the route set also carries the
body,queryandheadersa handler validates, so calls are checked more tightly than before:// server/api/users.post.ts validates { title: string, count: number } await $fetch('/api/users', { method: 'post', body: { title: 'a', count: 1 } }) await $fetch('/api/users', { method: 'post', body: { title: 'a', count: 'no' } }) // ^ not assignable to number await $fetch('/api/users', { method: 'post' }) // ^ body is requiredOn Nuxt 4 this is opt-in, because there are small changes to type inference, and hand-written
ServerRoutesaugmentations need a small rewrite. It is the default in Nuxt 5.export default defineNuxtConfig({ experimental: { routeTypedFetch: true, }, })There's also a new
experimental.strictRouteTypesoption to reject calls to paths that don't exist (otherwise these just returnunknown), and an'isomorphic'mode that types your pages asGETroutes too if you want to be able to$fetchfrom the Vue renderer with type safety.👉 Read more in the experimental features docs.
Better errors in development with
my-badServer-side errors in development used to look like this:
ReferenceError: foo is not defined at Object.<anonymous> (/_nuxt/app/pages/index.vue:1:1)There was no source position or code frame, and the Youch iframe we rendered could not show you the frame in your own source either. Both are now fixed (#36258, nuxt/cli#1518).
Dev SSR stack traces are now mapped before anything reads the error, and the Youch overlay has been replaced with
my-bad. It renders into your app's own error page as an overlay (or as a standalone page when the app can't render one), with the mapped stack trace and a code frame from your source, and the same report is printed in your terminal. We are still working with @atinux, @HugoRCD and @antfu to make these pages nicer still.With Nuxt CLI v4, there is a single live error channel at the CLI level. It survives worker restarts, so (for example) a syntax error in
nuxt.config.tswill live-reload the page once you fix it. Each error is rendered once rather than at every layer it passes through, and the same channel streams build progress and app logs to the dev panel.A new loading screen, 404 and error pages
@HugoRCD has redrawn the loading screen you see while the dev server starts. It is now a WebGL2 particle field that traces a mountain range behind the Nuxt lockup (#36178), using a single shader and a single draw call. Without WebGL2 it falls back to the static lockup, and with
prefers-reduced-motionthe animation stops. Try hovering over it. 🏔️Hugo also gave the built-in 404 and error pages a neutral palette and lighter type (#36255), and @MirkoJa added a back button to the 404 page (#35688).
Vue Vapor support
Nuxt now supports Vue 3.6's Vapor Mode in interop mode (#35759). Your app root stays on the virtual DOM, and you can opt individual components or pages into Vapor by adding the
vaporattribute to<script setup>:export default defineNuxtConfig({ vue: { vapor: true, }, })<script setup vapor lang="ts"> const count = ref(0) </script> <template> <button @click="count++"> count is {{ count }} </button> </template>Routing,
useAsyncData, layouts and most built-in components keep working unchanged. Along the way we made the auto-import loader,useAsyncData,definePageMetaand slot inspection Vapor-aware, and we now have a Vapor test suite so we can track what's supported.Note
This requires Vue
^3.6.0-rc.2or newer. See the known limitations and try it in a fresh project first.Addons for
useFetchanduseAsyncData@cernymatej has added an
addonsoption to thecreateUseFetchandcreateUseAsyncDatafactories (#35797). An addon can declare custom call-site options, adjust the merged options, wrap the handler with middleware, and extend what the composable returns, and it can be reused across as many custom instances as you like.const refreshOnFocus = defineUseFetchAddon({ setup: (options: UseFetchAddonOptions<{ refreshOnFocus?: boolean }>) => { if (import.meta.server || !options.refreshOnFocus) { return } return (asyncData) => { const focused = useWindowFocus() watch(focused, focused => focused && asyncData.refresh()) return { focused } } }, }) export const useApiFetch = createUseFetch({ baseURL: '/api', addons: [refreshOnFocus] })<script setup lang="ts"> const { data, focused } = await useApiFetch('/todos', { refreshOnFocus: true }) </script>This resolves a long list of feature requests for
useAsyncDataanduseFetch(refresh on focus, polling, retries, auth headers and more) without making the core composables opinionated about any of them.👉 Read about
defineUseFetchAddonanddefineUseAsyncDataAddon.Performance
There is a lot of performance work in this release.
<NuxtLink>renders 58% faster on the server (#36015). Internal links are now rendered as a plain<a>with nouseLink, no computed and no reactive state. Rendering 200 links went from 1.36ms to 0.57ms, which is 1.4x faster than a bare<RouterLink>.ssr: falsepages are tree-shaken from the server bundle (#35836, thanks to @Austin1serb).Serializable
definePageMetakeys are extracted at build time (#35919), behindexperimental.extractSerializablePageMeta.Lazy impound tracing for builds (#36172), virtual module hooks filtered by id (#36077),
isVuechecks migrated to plugin filters (#36116) and anflruprerender cache (#36340).
Put together, on our benchmark machine (arm64 Linux, Node 24.15, medians of 5 runs):
v4.5.2 v4.6.0 @nuxt/kitinstall size6.4 MB 2.1 MB -67% @nuxt/kittransitive dependencies36 22 -39% nuxt build, starter4.4 s 3.6 s -18% nuxt build, 200 pages / 200 components / 50 routes11.6 s 10.3 s -11% SSR throughput, page with 300 <NuxtLink>s110 req/s 140 req/s +26% Dev server start-up (spawn to first HTML) on the same machine is about 12% faster on a starter app, with the second request served in roughly half the time, though the CLI major changed alongside so not all of that is Nuxt.
Lighter payloads
useAsyncDataanduseFetchaccept aserialize: falseoption to keep data out of the__NUXT_DATA__payload (#35779). That's most useful inside components that never hydrate, andexperimental.stripNeverHydratedDataapplies it automatically to data fetched withinhydrate-nevercomponent trees.Nuxt also warns in development when a page's payload exceeds 100 kB (#35777) and when a route rendered with
noScriptsrelies on client-side JavaScript (#35780), andnoScriptspages keep their non-script resource hints and attach their styles correctly (#35803, #36356, #36359).<NuxtLink>now prefetches server-page islands (#35808), and @atinux made prefetch hints throttled and prioritised so a page full of links doesn't flood the network (#36261, #36324). Building on that, route chunks, layouts, middleware, payloads, islands and resource hints all now go through one client prefetch scheduler with per-kind concurrency caps, deduplication by key, and cancellation of in-flight work when you navigate away (#36391).Nuxt 5 features, today
Most of what's new in Nuxt 5 is already in 4.6, either as the default or behind a flag.
future.compatibilityVersion: 5turns on the Nuxt 5 defaults in one go, and every one of them can be enabled (or disabled) individually.export default defineNuxtConfig({ future: { compatibilityVersion: 5, }, })Newly gated behind the flag in this release:
Typed
$fetch(experimental.routeTypedFetch), described aboveCase-sensitive routing, matching Nitro (#35650, thanks to @Mateleo)
Early return from
navigateTo(experimental.navigateToEarlyReturn):navigateToin<script setup>short-circuits the rest of the setup, so redirects and 404s don't throw on missing dataNormalized page names,
clearNuxtStateresetting to defaults,experimental.watcher: 'builder', and no auto-imported server-only head composablesNo
baseUrlin generated tsconfigs (#36040, thanks to @oritwoen)
The upgrade guide now lists exactly what the flag changes on Nuxt 4.
Experimental:
@nuxt/vite-serverSince v4.2
server.builderhas been configurable. This release adds a second server builder:@nuxt/vite-server. It builds a Nuxt app with Vite alone (#36218, #36279, #36288).This is all you need to do to configure it.
export default defineNuxtConfig({ server: { builder: 'vite', // 'nitro' is the default }, })It can produce a pure client SPA, a server-rendered app with a small Node entry, a web-standard
fetchhandler for platforms that provide the server (there are e2e examples for Cloudflare Workers, Netlify and universal deploy), as well as fully static output withnuxt generate.Right now, this helps keep Nuxt's code agnostic, enforce the contract behind
nuxt/server, and to give Vite plugins that provide a deploy target something to build on. It does not have Nitro's full feature set (there is no storage, caching, tasks or server plugins), and we expect most apps to keep using Nitro. Nitro remains the default.Warning
This is highly experimental and the API will change.
'nitro'and'vite'are new shorthands for@nuxt/nitro-serverand@nuxt/vite-server.Developer experience
app/types/andserver/types/are included in the right tsconfig, so ambient types and augmentations placed there are picked up (#35783, thanks to @Flo0806, who also added an augmentableNuxtPageMetafor typingNuxtPage.metain #34816).Grouping folders in
components/: a(group)/folder is excluded from the component name (#35699, thanks to @abaza738).Dynamic
expiresinuseCookie, accepting a function (#35628, thanks to @DarlanPrado).A warning when a
public/file shadows an application route (#35674, thanks to @Norbiros).$Fetchis exported fromnuxt/app(#35625) andShallowRefis in the Vue auto-import preset (#36266), both from @DamianGlowala;preloadComponentsand theNuxtIslandnameprop are typed (#35775), anduseLayout,useLoadingIndicatoranduseRequestHeaderare exported fromnuxt/app(#36033).typescript.tsConfigis now a shared baseline for all four generated tsconfigs, withappTsConfigandserverTsConfigfor per-context overrides (#35697, thanks to @chairulakmal).Top-level
prerenderoption, an alias fornitro.prerenderin the same wayruntimeConfigandrouteRulesare top-level (#32356). Nuxt now also points you towards top-level options where they exist, since those work across server builders (#36416).Links to
public/files just work. If the router has no route for a<NuxtLink>target (a PDF inpublic/, say, or a link from Markdown with Nuxt Content), Nuxt falls through to a full-page load instead of rendering your 404, soexternalis no longer required (#36169).Renaming a component in development refreshes its imports, so you no longer see stale references to the old file (#36165, thanks to @oritwoen).
For module authors
If you maintain a module with server code, we've enabled making modules compatible with both Nuxt 4 & 5, without requiring a major bump. (And we'll be opening PRs proactively after the release of Nuxt v4.6 to assist with preparing for a Nuxt v5 release...)
useTerminalfor host-aware prompts, status messages and tasks in progress, rendered by the CLI's dev panel when there is one (#36162).module:beforeandmodule:donehooks, which Nuxt CLI v4 uses to show per-module setup time as it happens (#36173).onConfigResolvedanddiffNuxtConfigto see what changed between two config loads (#35853).ensureDependencyInstalledandgetAddDependencyCommandto check for and offer to install optional dependencies with the user's package manager (#34554).Template
dependenciesto say exactly what should invalidate a template (#35875).addServerImports,addServerImportsDirandaddServerTemplatework the same across Nitro versions; a server tsconfig and versioned route config types are generated for you (#36265).@nuxt/kithas an explicit public API (#36074) and@nuxt/schemais an optional peer (#36246).Modules can now set
experimental.asyncContext(#36175, thanks to @cernymatej), Vite plugins added via kit land at the top level rather than wrapped (#36037), and more build-time warnings have moved to diagnostic codes with docs pages (#36138).@nuxt/kitpeer dependency ranges are widened to the versions actually required rather than tracking the latest of each package (#36417), andupdateRuntimeConfigno longer warns when called before Nitro exists (#36403, thanks to @Neekoras).
Security
- Security
The internal error route is only served to an error render, and can no longer be reached from outside (259058cf4, #36305).
- Security
Dev error reports are scoped for remote peers, and the dev error channel is kept out of production builds (#36389, #36407).
- Security
Unhandled error data is no longer passed to the error page (38a40cfc0), oversized island bodies are drained before being rejected (#36320), and error-render recursion is tracked in request context rather than via a client-controllable header (d8c729435).
Important fixes
Awaited
useAsyncDatano longer resolves with unfetched data on hydration (#36124), awaited lazy async data resolves immediately (#36301), anduseAsyncDatatypes resolve for generic type params (#36316).useRequestFetchforwards request headers (#36180, thanks to @hdwebpros).navigateTomatches vue-router's path encoding (#36055), preserves percent-encoding in server redirects (#36112), and appliesbaseURLwithopen(#36197).Scoped styles apply to server component slots (#36047), island asset requests are deduped (#36048), lazy hydration no longer produces blank remounts (#36051), all from @oritwoen, and hydrated
nuxt-clientmarkup is stripped from cached island HTML (#36298).A batch of CSS fixes across Vite, webpack and rspack: duplicate CSS links for inlined chunks (#36056),
baseURLandurl()rewriting in inlined styles (#36137, #36143), island descendant CSS extraction (#36260) and stable style chunk names (#36361).View transitions handle interrupted and skipped navigations (#35537 from @Askerka00, #36314), and page transitions stay mounted for nested routes with no children (#36304).
The streaming shell head renders after the first render pass (#36120).
Payload URLs are parsed as origin-relative paths, so a path like
//x/_payload.jsonno longer serves the wrong payload (#36409, spotted/index.htmlis prerendered for client-only apps with islands (#36299).definePageMetaworks at the top level ofsetup()(#36245), and changed auto-import sources are rescanned before their consumers (#33671, thanks to @Flo0806).A template that never finishes compiling now fails the build instead of exiting 0 (#36322).
Error causes are preserved in development (#35632, thanks to @onmax).
Layout
onBeforeLeavereuses the pending transition promise (#36395), andbaseURLand middleware flags are respected in apps withoutpages/(#36034).stripNeverHydratedDatano longer mutates the options object (#36035), the dev error module is stubbed out of production builds (55e61d75d), and preloading a component that is not global now warns (47de80ece).
Upgrading
Our recommendation for upgrading is to run:
npx nuxt upgrade --dedupe
This will refresh your lockfile and pull in all the latest dependencies that Nuxt relies on, including Nuxt CLI v4.
Note
This release requires Node.js
^22.22.3 || ^24.15.0 || >=26.0.0.If you have server code you'd like to make portable, read Moving to
nuxt/serverin the upgrade guide.Changelog
Enhancements
kit,nitro,nuxt,rspack,vite,webpack: use package manager in hints
Performance
kit: remove
confboxandpkg-typesfrom dependencies
Fixes
- Deprecated
schema: deprecate
nitro.*options duplicated at the top level rspack,webpack: do not serve server bundle from dev server
rspack,webpack: respect inlineStyles predicate for global css
rspack,webpack: do not search filesystem for postcss config
rspack,webpack: keep url() wrapper when rewriting inlined styles
4.5.2
5 Aug 20264.5.1
27 Jul 2026rspack,webpack: Resolve loaders and runtime deps from nuxt dirs
kit,nuxt,rspack,schema,webpack: Add
.mtsfile extension in resolvernuxt: Remove dev error overlay when error is cleared
⚠️ This is a security release. We recommend upgrading as soon as possible with
npx nuxt upgrade --dedupe.It fixes server-side RCE and unauthorized component instantiation via server island props, a route rule authorization bypass, server component DoS, cross-user payload disclosure on cached pages, and dev server path disclosure. Refreshing your lockfile also pulls in
@nuxt/devtools@3.3.1, which fixes a separate critical development-only RCE.If you already upgraded for the earlier route rule advisory (CVE-2026-53721), you still need this release: one of the fixes addresses a regression introduced by that fix.
If you use the
cache,swrorisrroute rules, purge any CDN or edge cache after upgrading; a leaked_payload.jsonmay already be cached upstream.Full details: Nuxt Security Patch Releases and GitHub Security Advisories.
Changelog
Fixes
rspack,webpack: Resolve loaders and runtime deps from nuxt dirs
kit,nuxt,rspack,schema,webpack: Add
.mtsfile extension in resolvernuxt: Remove dev error overlay when error is cleared
rspack,webpack: Resolve bundled postcss defaults from builder
4.5.0
18 Jul 2026The dev server now runs in middleware mode via Rsbuild, replacing
webpack-dev-middlewareandwebpack-hot-middleware(#35575).We use an Rspack-specific Vue loader for correct SSR scoped-style ids and stricter ESM resolution (#35566).
nuxt module removeto uninstall a module and clean up its config (nuxt/cli#1306), the natural companion tonuxt module add.
4.5.0 is the next minor release.
Some News
Preparing for Nuxt 5
A good chunk of this release is (hopefully) invisible plumbing for Nuxt 5. We've moved onto the latest major versions of several core dependencies (
unheadv3,unctxv3, and Vite 8), switched the framework's own build over totsdown, and introduced a stablenuxt/*build output contract with dev exports so that type-checking in the Nuxt monorepo works without a build step (#35463, #35605).Much of this is working to shrink the gap between v4 and v5 internally, so that the migration will be as boring as possible.
Tip
If you want to test some of the breaking changes of Nuxt v5, you can already opt in with
future.compatibilityVersion: 5. Keep an eye on the Upgrade Guide for details as they land.With the release of Nuxt v4.5, our focus as a team will turn to stabilising Nuxt v5 and creating compatibility utilities to make the upgrade as smooth as possible.
Nuxt 3 End-of-Life
Nuxt 3 reaches end-of-life on July 31, 2026, so this is one of the last few 3.x releases we'll ship. If you're still on v3, now is a great time to move across. Most people told us the v3 to v4 upgrade was smooth, and we've kept the upgrade guide up to date.
Alongside v4.5.0 we're publishing a maintenance patch for the 3.x line (v3.21.9) with the compatible bug fixes and smaller improvements from this release backported. The headline items here (Vite 8, Rspack 2,
unheadv3,unctxv3) are major upgrades and stay v4-only, so 3.x remains stable as it approaches end-of-life.Highlights
Nuxt 4.5 is a big one. This release ships three major upgrades to the build layer (Vite 8, Rspack 2, and a brand new Rsbuild-powered pipeline for the Rspack builder), an experimental SSR streaming mode, a handful of new composables and conventions, and a lot of groundwork that brings us closer to Nuxt 5.
There's a lot here, so grab a coffee. ☕️
Vite 8
Nuxt now runs on Vite 8 (#34256). This brings faster cold starts, the latest Rolldown-powered internals, and many upstream improvements from the Vite team.
For most apps this is a transparent upgrade. If you have custom Vite plugins or config, it's worth skimming the Vite migration guide to check for anything that affects you.
Warning
Vite 8 is a major version bump. If you depend on Vite directly (custom plugins,
vite.configtweaks, or ecosystem plugins that pin a Vite version), make sure those are compatible before upgrading in production.Rspack 2 and Rsbuild
If you use the Rspack builder, this release is a substantial upgrade. We've moved to Rspack 2 (#34929), which is faster and lighter, and rebuilt the builder on top of
@rsbuild/core(#35489).The public surface stays the same. You still opt in with
builder: 'rspack'and the existingrspack:*hooks continue to work:// nuxt.config.ts export default defineNuxtConfig({ builder: 'rspack', })Under the hood, though, a lot has changed for the better:
The dev server now runs in middleware mode via Rsbuild, replacing
webpack-dev-middlewareandwebpack-hot-middleware(#35575).We use an Rspack-specific Vue loader for correct SSR scoped-style ids and stricter ESM resolution (#35566).
Note
This is the foundation for first-class Rsbuild support. We kept the builder named
rspackfor now so nothing breaks, but the internals are now Rsbuild all the way down.Experimental SSR Streaming
This is one I'm particularly excited about. You can now enable SSR streaming to dramatically improve Time to First Byte (#34411). Instead of buffering the whole rendered page and sending it in one go, Nuxt flushes the HTML shell (your
<head>, styles, preload hints, and entry scripts) immediately, then streams the body as Vue renders it.// nuxt.config.ts export default defineNuxtConfig({ experimental: { ssrStreaming: true, }, })Streaming is automatically disabled for bots and crawlers so search engines still receive fully-rendered HTML. You can tune which user agents count as crawlers, and you can opt individual routes out:
// nuxt.config.ts export default defineNuxtConfig({ experimental: { ssrStreaming: { botRegex: /googlebot|bingbot|my-internal-crawler/i, }, }, routeRules: { '/no-stream/**': { streaming: false }, }, })There's one thing worth understanding before you turn it on. Because streaming commits the HTTP status and headers with the very first byte, anything that mutates the response after rendering has begun (a
setResponseStatus()in a<script setup>, a cookie write during middleware, and so on) can't reach the client. Nuxt handles the common cases for you: routes withredirect,cache,isr,swr,noScripts, orssr: falserules automatically fall back to the buffered renderer, and in development we log a warning naming any dropped mutations so nothing fails silently.Warning
SSR streaming is experimental and off by default. It could be great for content-heavy routes where TTFB matters, but test it against your app's response-mutating logic (status codes, headers, cookies) before shipping it widely. The experimental features docs cover the fallback rules and caveats in detail.
Stable Error Codes
This one I'm really happy about. Nuxt now has a stable error code system (#35429). Warnings and errors raised during build and at runtime now carry a stable code (like
NUXT_E1001orNUXT_B5001), a short explanation of why it happened, and a concrete fix to try.Every code is greppable and bookmarkable, and the ones that need more than a one-line fix link straight to a dedicated docs page. For example, the classic "a composable was called outside a Nuxt context" now surfaces as
NUXT_E1001with the why/fix inline and a docs page explaining the context rules and how to userunWithContext().To keep production output lean, the verbose why/fix text is stripped from production builds, leaving just the stable code.
This is the foundation for much better error messages across Nuxt, and we'll keep migrating existing warnings and errors onto it over the coming releases. If you've ever squinted at a cryptic Nuxt message, this is for you.
useLayoutComposableThere's a new
useLayoutcomposable for reading the layout that's been resolved for the current route (#35623). Previously there was no clean, reactive way to ask "which layout is this page using?" from within a component.<!-- app/components/LayoutBadge.vue --> <script setup lang="ts"> const layout = useLayout() </script> <template> <span>Current layout: {{ layout }}</span> </template>It returns a read-only computed ref, so it stays in sync as you navigate or as route rules and
definePageMetachange the resolved layout.Named Views
Nuxt now supports named views through a filename convention (#35123). If a parent page renders more than one
<NuxtPage>outlet, you can give each outlet a name and provide a sibling page file for it using thename@view.vueconvention:# Directory Structure -| pages/ ---| parent/ -----| child.vue -----| child@sidebar.vue ---| parent.vue
<!-- pages/parent.vue --> <template> <div> <NuxtPage /> <aside> <NuxtPage name="sidebar" /> </aside> </div> </template>Navigating to
/parent/childrenderschild.vueinto the default outlet andchild@sidebar.vueinto thesidebaroutlet. This has actually been possible in Vue Router for a long time; this release wires it up to Nuxt's file-based routing.Note
definePageMetais read from the default route file only, and per-view rendering modes aren't supported (the parent page's mode applies to the default view).enabledOption foruseFetchanduseAsyncDataYou can now gate data fetching with a reactive
enabledoption (#33260). Whileenabledisfalse, every execution is blocked (the initial fetch,execute/refresh, and watch triggers), and if you flip it fromtruetofalsemid-flight, the in-flight request is cancelled without clearing your existingdata.<script setup lang="ts"> const query = ref('') const { data } = await useFetch('/api/search', { query: { q: query }, // Only fetch once the user has typed something enabled: () => query.value.length > 2, }) </script>This is perfect for dependent or conditional queries, where you don't want to fire a request until some precondition is met. It pairs naturally with a getter or a ref, so it stays reactive.
NuxtLinkPrefetch Control for Custom SlotsWhen you use
<NuxtLink>with thecustomprop, Nuxt no longer attaches prefetch handlers for you, because it can't know how you've structured your markup. To make that ergonomic, the slot now exposes everything you need to wire prefetching up yourself (#34539):<template> <NuxtLink v-slot="{ href, navigate, prefetch, prefetched, shouldPrefetch }" to="/about" custom > <a :href="href" :class="{ 'is-prefetched': prefetched }" @click="navigate" @pointerenter="shouldPrefetch('interaction') && prefetch()" @focus="shouldPrefetch('interaction') && prefetch()" > About page </a> </NuxtLink> </template>You get
prefetchto trigger it,prefetchedto know whether it's already happened (great for a prefetched class), andshouldPrefetchto respect the user's connection and config.Forwarded Preload Hints on Prefetch
Here's another one we'd love you to try. When you prefetch a link to a route with payload extraction, Nuxt already primes the destination's data and chunks. With the new opt-in
experimental.prefetchPreloadTags(#35144), it also forwards the destination's<link rel="preload">andmodulepreloadhints (whatever the page sets viauseHead, or via modules like@nuxt/image's<NuxtImg preload>) into the current document, downgraded torel="prefetch"so they don't compete with the resources the user is looking at right now.// nuxt.config.ts export default defineNuxtConfig({ experimental: { prefetchPreloadTags: true, }, })The practical effect is that heavy above-the-fold assets on the next page (a hero image, a critical script) start downloading while the user is still on the current one, so the navigation feels instant. It's off by default while we gather feedback, so please give it a spin and tell us how it behaves on your app.
import.meta.envNameThe resolved Nuxt environment name is now available at runtime as
import.meta.envNamefor both Vite and webpack/Rspack builds (#34844). This is the value set by--envName(or the resolved default), so you can branch on it in your app code:if (import.meta.envName === 'staging') { // enable staging-only behaviour }Tracing Channels for SSR Events
Nuxt now publishes diagnostics-channel traces for its server-side subsystems (#35191). It's unopinionated: we emit
nuxt.render,nuxt.island,nuxt.data, andnuxt.pluginchannels following the untracing naming convention, and you can build OpenTelemetry (or anything else) on top. It works in Node, Deno, Bun, and Cloudflare Workers.// nuxt.config.ts export default defineNuxtConfig({ // Turn on Nuxt's own channels tracingChannel: true, })You can also enable it granularly. In Nuxt v5, there will be additional Nitro-level channels:
// nuxt.config.ts export default defineNuxtConfig({ tracingChannel: { nuxt: true, }, })Note
Channel names, payload shapes, and option keys may still change while the untracing registry settles.
Dependency Upgrades
unheadv3Nuxt's head management now runs on
unheadv3 (#34793). It's smaller, uses a synchronous engine internally, and ships better type-safety foruseHeadout of the box. This also unblocks SSR streaming.Warning
unheadv3 introduces type-narrowing foruseHead, which can be a breaking type change if you were relying on the looser v2 types. The runtime behaviour is compatible for the vast majority of apps, and promise input (deprecated in v2) is no longer supported. If you hit type errors after upgrading, they're almost always genuine tightening rather than regressions.unctxv3We've moved to
unctxv3 (#35541), which resolves a class of long-standing async context issues (#33644). This is part of the composable-context reliability work that continues into v5.And more
We've also updated
magic-stringto v1, Babel to v8, and pulled in the latest Rolldown across the board. Runningnuxt upgrade --dedupe(see below) is the easiest way to pull these through cleanly.Nuxt CLI
This release bundles some improvements from
@nuxt/cliv3.36 and v3.37:nuxt module removeto uninstall a module and clean up its config (nuxt/cli#1306), the natural companion tonuxt module add.Non-interactive
nuxt initfor scripting and CI (nuxt/cli#1341), plus it now respects the template's own package manager instead of prompting (nuxt/cli#1330).
TypeScript Plugin and Named Layout Slots
Nuxt's experimental TypeScript plugin is powered by
@dxup/nuxt, and this release bundles a newer version of it. If you haven't tried it, turning onexperimental.typescriptPlugingives you a set of editor niceties: renaming an auto-imported component updates every usage, plus go-to-definition for glob imports, Nitro routes,definePageMeta,runtimeConfig, and typed route names.New in the bundled version is an opt-in runtime feature: named layout slots (KazariEX/dxup#20). You can write a top-level named-slot template in a page and have it forwarded into the matching named slot of the active layout. That lets a page inject content into its layout's slots, which file-based layouts don't otherwise allow.
Enable it alongside the plugin:
// nuxt.config.ts export default defineNuxtConfig({ experimental: { typescriptPlugin: true, }, dxup: { features: { namedLayoutSlots: true, }, }, })Then a layout can expose named slots:
<!-- layouts/center.vue --> <template> <slot /> <slot name="side" one="one" /> </template>
And any page using that layout can fill them:
<!-- pages/about.vue --> <script setup lang="ts"> definePageMeta({ layout: 'center' }) </script> <template> <template #side="{ one }"> This "{{ one }}" comes from the layout slot. </template> <div>About page</div> </template>📖
typescriptPlugindocumentationPerformance and Reliability
As always, a lot of work has gone into making Nuxt faster and steadier.
One you can opt into today is the shared file watcher (#35143). Vite already runs a chokidar-based watcher, so Nuxt can piggy-back on it instead of spinning up a second one, using less memory and fewer file handles. This becomes the default with
compatibilityVersion: 5, but you can turn it on now and let us know how it goes:// nuxt.config.ts export default defineNuxtConfig({ experimental: { watcher: 'builder', }, })There are also some other good performance improvements that don't need to be opted into:
A couple of other nice quality-of-life fixes:
$fetchis now auto-imported in user code, which fixes edge cases with top-level$fetch.createunder Rolldown's output format (#35581).Nuxt now honours system
HTTP_PROXY/HTTPS_PROXYenvironment variables in the builder environment (#35183).HMR now works for
defineNuxtComponentin JSX (#35620).
Heads-Up Before Upgrading
As mentioned above, this release includes three major dependency bumps. For most apps they're transparent, but they're worth a moment of attention:
unheadv3: possible breaking type changes from stricteruseHeadtyping.
Upgrading
Our recommendation for upgrading is to run:
npx nuxt upgrade --dedupe # or, if you are staying on the 3.x line npx nuxt@latest upgrade --dedupe --channel=v3
This will deduplicate your lockfile and help ensure you pull in updates from the other dependencies Nuxt relies on, particularly across the unjs ecosystem (which matters more than usual this release, given the major bumps).
Tip
Check out our upgrade guide if you're upgrading from an older version.
Thank you to all of the many contributors to this release. This was a big one, and it wouldn't happen without you. 💚
Changelog
Enhancements
rspack: Upgrade to rspack v2
rspack: Use rspack-specific Vue loader
rspack: Use rspack-specific Vue loader
rspack: Use rsbuild dev server in middleware mode
Error code system
Performance
nuxt,rspack,vite,webpack: Migrate to
rolldown-stringnitro,nuxt,vite: Remove unused dependencies
Fixes
rspack,webpack: Strip invalid webpack PURE annotations
rspack,webpack: Use async entry in dev to avoid circular import
4.4.8
8 Jun 2026vite: Shorter socket name for macOs with tmp fallback
kit: Respect
typeoption infindPathdeps: Update nuxt/scripts presets
4.4.8 is a hotfix release to address an issue running the dev server on MacOS.
Changelog
Fixes
vite: Shorter socket name for macOs with tmp fallback
kit: Respect
typeoption infindPathdeps: Update nuxt/scripts presets
nuxt: Revert unhead dependency back to v2
4.4.7
2 Jun 2026rspack,webpack: Require loopback host when missing same-origin signals
4.4.7 is a security hotfix release.
👉 make sure to check github.com/nuxt/nuxt/security/advisories to view open advisories resolved by this release.
Changelog
Fixes
rspack,webpack: Require loopback host when missing same-origin signals
4.4.6
18 May 20264.4.5
10 May 20264.3.1
7 Feb 2026Only enable dynamic imports when ts plugin
4.3.1 is a regularly scheduled patch release.
Changelog
Fixes
Only enable dynamic imports when ts plugin
4.3.0
22 Jan 2026- Removed
Remove babel debugging plugin from jiti stub options
Continue making pull requests to the
mainbranchWe'll backport changes to the
4.xand3.xbranches
4.3.0 is the next minor release.
Nuxt 4.3 brings powerful new features for layouts, caching, and developer experience – plus significant performance improvements under the hood.
Some News
Extended v3 Support
Early this month, I opened a discussion to find out how the upgrade had gone from v3 to v4. I was really pleased to hear how well it had gone for most people.
Having said that, we're committed to making sure no one gets left behind. And so we will continue to provide security updates and critical bug fix releases beyond the previously announced end-of-life date of January 31, 2026, meaning Nuxt v3 will meet its end-of-life on July 31, 2026.
Tip
As usual, today also brings a minor release for v3, with many of the same improvements backported from v4.3.
Preparing for Nuxt 5
We're closer than ever to the releases of Nuxt v5 and Nitro v3. In the coming weeks, the
mainbranch of the Nuxt repository will begin receiving initial commits for Nuxt 5. However, it's still business as usual.Continue making pull requests to the
mainbranchWe'll backport changes to the
4.xand3.xbranches
Keep an eye out on the Upgrade Guide – we'll be adding details about how you can already start migrating your projects to prepare for Nuxt v4 with
future.compatibilityVersion: 5.Route Rule Layouts
But that's enough about the future. We have a lot of good things for you today!
First, you can now set layouts directly in route rules using the new
appLayoutproperty (#31092). This provides a centralized, declarative way to manage layouts across your application without scatteringdefinePageMetacalls throughout your pages.export default defineNuxtConfig({ routeRules: { '/admin/**': { appLayout: 'admin' }, '/dashboard/**': { appLayout: 'dashboard' }, '/auth/**': { appLayout: 'minimal' } } })This might be useful for:
Admin panels with a shared layout across many routes
Marketing pages that need a different layout from the app
Tip
Plus, you can pass props to layouts now! See the
setPageLayoutimprovements below.ISR/SWR Payload Extraction
Payload extraction now works with ISR (incremental static regeneration), SWR (stale-while-revalidate) and cache
routeRules(#33467). Previously, only pre-rendered pages could generate_payload.jsonfiles.This means:
Client-side navigation to ISR/SWR pages can use cached payloads
CDNs (Vercel, Netlify, Cloudflare) can cache payload files alongside HTML
Fewer API calls during navigation – data can be prefetched and served from the cached payload
export default defineNuxtConfig({ routeRules: { '/products/**': { isr: 3600, // Revalidate every hour } } })Dev Mode Payload Extraction
Related to the above, payload extraction now also works in development mode (#30784). This makes it easier to test and debug payload behavior without needing to run a production build.
Important
Payload extraction works in dev mode with
nitro.staticset totrue, or for individual pages which haveisr,swr,prerenderorcacheroute rules.Disable Modules from Layers
When extending Nuxt layers, you can now disable specific modules that you don't need (#33883). Just pass
falseto the module's options:export default defineNuxtConfig({ extends: ['../shared-layer'], // disable @nuxt/image from layer image: false, })Route Groups in Page Meta
Route groups (folders wrapped in parentheses like
(protected)/) are now exposed in page meta (#33460). This makes it easy to check which groups a route belongs to in middleware or anywhere you have access to the route.<script setup lang="ts"> // This page's meta will include: { groups: ['protected'] } useRoute().meta.groups </script>export default defineNuxtRouteMiddleware((to) => { if (to.meta.groups?.includes('protected') && !isAuthenticated()) { return navigateTo('/login') } })This provides a clean, convention-based approach to route-level authorization without needing to add
definePageMetato every protected page.Layout Props with
setPageLayoutThe
setPageLayoutcomposable now accepts a second parameter to pass props to your layout (#33805):export default defineNuxtRouteMiddleware((to) => { setPageLayout('admin', { sidebar: true, theme: 'dark' }) })<script setup lang="ts"> defineProps<{ sidebar?: boolean theme?: 'light' | 'dark' }>() </script>#serverAliasA new
#serveralias provides clean imports within your server directory (#33870), similar to how#sharedworks:// Before: relative path hell import { helper } from '../../../../utils/helper' // After: clean and predictable import { helper } from '#server/utils/helper'The alias includes import protection – you can't accidentally import
#servercode from client or shared contexts.Draggable Error Overlay
The development error overlay introduced in Nuxt 4.2 is now draggable and can be minimized (#33695). You can:
Drag it to any corner of the screen (it snaps to edges)
Minimize it to a small pill button when you want to keep working
Your position and minimized state persist across page reloads
This is a quality-of-life improvement when you're iterating on fixes and don't want the overlay blocking your view.
github.com/user-attachments/assets/nuxt_4-3_err…
Async Plugin Constructors
Module authors can now use async functions when adding build plugins (#33619):
export default defineNuxtModule({ async setup() { // Lazy load only when actually needed addVitePlugin(() => import('my-cool-plugin').then(r => r.default())) // No need to load webpack plugin if using Vite addWebpackPlugin(() => import('my-cool-plugin/webpack').then(r => r.default())) } })This enables true lazy loading of build plugins, avoiding unnecessary code loading when plugins aren't needed.
Performance Improvements
This release includes several performance optimizations for faster builds:
Hook filters - Internal plugins now use filters to avoid running hooks unnecessarily
SSR styles optimization - The
nuxt:ssr-stylesplugin is now significantly faster (#33862, #33865)Layer alias transform - Skipped when using Vite (it handles this natively)
Route rules compilation - Route rules are now compiled into a client chunk using
rou3, removing the need forradix3in the client bundle and eliminating app manifest fetches
Inline Styles for Webpack/Rspack
The
inlineStylesfeature now works with webpack and rspack builders (#33966), not just Vite. This enables critical CSS inlining for better Core Web Vitals regardless of your bundler choice.Deprecations
statusCode→status,statusMessage→statusTextIn preparation for Nitro v3 and H3 v2, we're moving to use Web API naming conventions (#33912). The old properties still work but are deprecated in advance of v5:
- throw createError({ statusCode: 404, statusMessage: 'Not Found' }) + throw createError({ status: 404, statusText: 'Not Found' })Bug Fixes
Notable fixes in this release:
Fixed head component deduplication using
keyattribute (#33958, #33963)Fixed async data properties not being reactive in Options API
Fixed
useCookieunsafe number parsing during decodeFixed
NuxtPagenot re-rendering when nestedNuxtLayouthas layouts disabledFixed client-side pathname decoding for non-ASCII route aliases
Fixed suspense remounting when navigating after pending state
Fixed clipboard copy in error overlay
Enabled
allowArbitraryExtensionsby default in TypeScript configAdded
noUncheckedIndexedAccessto server tsconfig for safer typing
Important
Enabling
noUncheckedIndexedAccessin the Nitro server TypeScript config improves type safety but may surface new type errors in your server code. This change was necessary because Nuxt's app context performs type checks on server routes (learn more).While we recommend keeping this enabled for better type safety, you can disable it if needed:
export default defineNuxtConfig({ nitro: { typescript: { tsConfig: { compilerOptions: { noUncheckedIndexedAccess: false } } } } })Note that disabling this may allow type errors to slip through that could cause runtime issues with indexed access.
Nuxt 3.21.0
Alongside v4.3.0, we're releasing Nuxt v3.21.0 with many of the same improvements backported to the 3.x branch. This release includes:
All the same features: Route rule layouts, ISR payload extraction, layout props with
setPageLayout,#serveralias, draggable error overlay, and moreAll performance improvements: SSR styles optimization, hook filters, and route rules compilation
Module disabling: Disable layer modules by setting options to
falseCritical bug fixes: Async data reactivity in Options API,
useCookienumber parsing, head component deduplication, and more
Upgrading
Our recommendation for upgrading is to run:
npx nuxt upgrade --dedupe # or, if you are upgrading to v3.21 npx nuxt@latest upgrade --dedupe --channel=v3
This will deduplicate your lockfile and help ensure you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
Tip
Check out our upgrade guide if upgrading from an older version.
Changelog
Enhancements
kit: Support async constructor for adding plugins
kit: Export Nuxt major version type
schema: Add
#serveralias for server directory importsui-templates: Let it snow! ❄️
schema: Hoist nitro
crosswstypesnitro,nuxt: Compile route rules into client chunk
nuxt: Allow disabling modules by setting module options to
falsekit: Allow specifying
moduleDependenciesas an async functionnuxt: Support
appLayoutin route rulesnuxt: Add route groups to page meta
nuxt: Enable payload extraction for ISR/SWR routes
nuxt: Allow updating props with
setPageLayoutnuxt: Enable dragging and minimizing for error overlay
nitro,nuxt: Add support for payload extraction in dev
rspack,webpack: Add inline styles
kit: Add forward-compatible nitro types
Performance
nuxt: Do not init layer alias transform when using vite
vite: Add hook filters for ssr styles plugin
vite: Optimize
nuxt:ssr-stylespluginnuxt: Use filter for vfs plugin load
nuxt,vite: Use filters to avoid running hooks unnecessarily
nuxt,vite: Add more filters to internal plugins
Fixes
kit: Normalize local layer paths with trailing slashes
nuxt: Avoid overwriting multiple head input in island handler
nuxt: Update meta instead of calling
router.replacein page hmrnuxt: Don't call
page:loading:endin cache if already calledvite: Add error handling for parsing
NUXT_VITE_NODE_OPTIONSnuxt: Do not skip middleware when
appMiddlewarereferences invalid keynitro: Clipboard copy in error overlay
webpack,rspack: Resolve deep imports in virtual files
webpack: Disable async chunks in dev mode
webpack: Correctly evaluate sourcemap name
nuxt: Handle node10 resolution for
nuxt/metanuxt: Do not early return if component priorities conflict
nuxt: Use
keyfor tag deduplication in<Head>componentschema,vite: Resolve
build.transpilewhen initialising vitenuxt,rspack,webpack: Inject module identifiers for webpack builders
nuxt: Add key to head components for proper deduplication
nitro: Check prettyResponse.body type before error overlay
nuxt: Don't URI-encode static route paths
nuxt: Skip internal stub routes from prerender
kit,schema: Align module
onUpgradearguments with typesnuxt: Handle unsafe number parsing in useCookie decode
nuxt: Do not externalise
rou3nitro: Add
noUncheckedIndexedAccessto server tsconfignuxt: Add auto-import declarations for
shared/contextnuxt: Update global reference to globalThis in
useRequestFetchvite: Configure hmr port for server build
kit: Add forward compatible nitro v3 types
nitro,nuxt: Do not import nitro deps in builders
nitro: Add
h3types to auto-importsschema: Add some more directories to ignore
nitro: Also augment
nuxt/schemanuxt: Make asyncData properties reactive in Options API
nuxt: Rerender
NuxtPagewhen nestedNuxtLayouthas explicitly disabled layoutskit,nitro: Enable
allowArbitraryExtensionsby defaultnuxt: Decode client-side pathname for non-ASCII route aliases
nuxt: Force remount suspense when navigating after pending
nuxt: Add documentation link to server builder error message
nuxt: Validate placeholder/fallback tags + warn about placeholder/fallback props
nuxt: Force flush
useAsyncDatadebounced execute post watcher flushnitro: Process isr/swr/cache keys
nuxt: Add
typeFromsupport forimports.d.tstemplate exportsnuxt: Ensure we inline styles for
hydrate-nevercomponents
Build
- Removed
Remove babel debugging plugin from jiti stub options
4.2.2
9 Dec 2025nitro: Do not show pretty error handler when testing
nuxt: Generate valid references for component declaration items
nuxt: Sync internal route before calling
page:finishhook
4.2.2 is the next patch release.
Upgrading
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.
Changelog
Fixes
nitro: Do not show pretty error handler when testing
nuxt: Generate valid references for component declaration items
nuxt: Sync internal route before calling
page:finishhookkit: Add TypeScript path alias support for test files
nitro: Ensure html is a string before injecting error handler
nitro: Include layer server directories in
tsconfig.server.jsonnuxt: Ensure deduped async data executions return latest promise
kit,nuxt: Type + respect
moduleDependenciesby meta namenuxt,schema: Ignore
.d.vue.tsdeclarationskit,nuxt: Protect against resolved nuxt module subpath
nuxt: Re-execute
callOnceduring HMRnuxt: Resolve watch callback after reactive key change in
useAsyncDatanuxt: Escape HTML in development error page stack trace
kit: Do not add resolved
rootDirto cached layer configkit,schema: Add
moduleDependencies->installModule
4.2.1
6 Nov 2025- Deprecated
kit,nuxt,schema: Deprecate
ImportPresetWithDeprecation nuxt: Correct warning message for prefetch/noPrefetch conflict
nitro: Remove
<nuxt-error-overlay>iframe border
4.2.1 is the next patch release.
Upgrading
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.
Changelog
Fixes
- Deprecated
kit,nuxt,schema: Deprecate
ImportPresetWithDeprecation nuxt: Correct warning message for prefetch/noPrefetch conflict
nitro: Remove
<nuxt-error-overlay>iframe bordervite: Use rolldown replace only in build
nitro: Use directory paths in
moduleEntryPathsnitro: Start error overlay minimized based on status code
vite: Ensure
optimizeDepsconfig is applied before other pluginsnuxt: Respect layer priority order for scanned components
nuxt: Process prerender routes on
pages:resolvednuxt: Remove abort signal event listeners after render
nuxt: Cleanup event listener with cleanup signal
vite: Update
vite-nodevite: Respect vite proxy in dev middleware
4.2.0
25 Oct 2025- Removed
nuxt: Remove
declarationPathfrom component dirs - Deprecated
schema: Deprecate
extend,extendConfig, andconfigResolvedhooks - Removed
Remove deprecated node version
4.2.0 is the next minor release.
Highlights
We're excited to announce Nuxt 4.2, bringing new capabilities for better TypeScript DX, enhanced error handling, and improved control over data fetching! 🎉
Abort Control for Data Fetching
You can now use
AbortControllersignals directly withinuseAsyncData, giving you fine-grained control over request cancellation (#32531).This works by passing an internal signal to your
useAsyncDatahandlerto cancel any promise that can be canceled, such as$fetch.<script setup lang="ts"> const controller = new AbortController() const { data, error, clear, refresh } = await useAsyncData('users', (_nuxtApp, { signal }) => $fetch('/api/users', { signal })) refresh() // will actually cancel the $fetch request (if dedupe: cancel) refresh() // will actually cancel the $fetch request (if dedupe: cancel) refresh() clear() // will cancel the latest pending handler </script>You also pass an
AbortControllersignal directly torefresh/execute, giving you fine-grained control over request cancellation. This is particularly useful when you need to abort requests based on user actions or component lifecycle events.const { data, refresh } = await useAsyncData('posts', fetchPosts) // Abort an ongoing refresh const abortController = new AbortController() refresh({ signal: abortController.signal }) // Later... abortController.abort()Better Error Pages in Development
When an error occurs during development, Nuxt will now display both your custom error page and a detailed technical error overlay (#33359). This gives you the best of both worlds – you can see what your users will experience while also having immediate access to stack traces and debugging information.
Screenshot of the new development error page
The technical overlay appears as a toggleable panel that doesn't interfere with your custom error page, making it easier to debug issues while maintaining a realistic preview of your error handling.
Opt-in Vite Environment API
For those wanting to experiment with cutting-edge features, you can now opt into the Vite Environment API (#33492).
The Vite Environment API is a major architectural improvement in Vite 6. It closes the gap between development and production by allowing the Vite dev server to handle multiple environments concurrently (rather than requiring multiple Vite dev servers, as we have done previously in Nuxt).
This should improve performance when developing and eliminate some edge case bugs.
... and it is the foundation for implementing Nitro as a Vite environment, which should speed up the dev server still further, as well as allowing more greater alignment in development with your Nitro preset.
export default defineNuxtConfig({ experimental: { viteEnvironmentApi: true } })This is also the first breaking change for Nuxt v5. You can opt in to these breaking changes by setting
compatibilityVersionto5:export default defineNuxtConfig({ future: { compatibilityVersion: 5 }, })Please only use this for testing, as this opts in to unlimited future breaking changes, including updating to Nitro v3 once we ship the Nuxt integration.
Warning
This is highly experimental and the API may change. Only enable if you're prepared for potential breaking changes and want to help shape the future of Nuxt!
New
@nuxt/nitro-serverPackageWe've extracted Nitro server integration into its own package:
@nuxt/nitro-server(#33462). This architectural change allows for different Nitro integration patterns and paves the way for future innovations in server-side rendering.While this change is mostly internal, it's part of our ongoing effort to make Nuxt more modular and flexible. The new package provides standalone Nitro integration and sets the foundation for alternative integration approaches (such as using Nitro as a Vite plugin in Nuxt v5+).
Note
This is an internal refactor – no changes should be required in your code.
Performance Improvements
We've also shipped several performance enhancements:
Reduced dependencies – Removed unnecessary dependencies from kit and schema packages
Async Data Handler Extraction
One of the most exciting performance improvements is the new experimental async data handler extraction (#33131). When enabled, handler functions passed to
useAsyncDataanduseLazyAsyncDataare automatically extracted into separate chunks and dynamically imported.This is particularly effective for prerendered static sites, as the data fetching logic is only needed at build time and can be completely excluded from the client bundle.
Note
In testing with a previous version of nuxt.com, this feature reduced JavaScript bundle size by 39%! Of course, your mileage may vary depending on how much data fetching logic you have.
<script setup lang="ts"> // This handler will be extracted into a separate chunk // and only loaded when needed const { data: post } = await useAsyncData('post', async () => { const content = await queryContent(`/blog/${route.params.slug}`).findOne() // Complex data processing that you don't want in the client bundle const processed = await processMarkdown(content) const related = await findRelatedPosts(content.tags) return { ...processed, related } }) </script>For static/prerendered sites, enable it in your config:
export default defineNuxtConfig({ experimental: { extractAsyncDataHandlers: true } })The extracted handlers are then tree-shaken from your client bundle when prerendering, as the data is already available in the payload. This results in significantly smaller JavaScript files shipped to your users.
Experimental TypeScript Plugin Support
We're introducing experimental support for enhanced TypeScript developer experience through the
@dxup/nuxtmodule.This module adds a number of TypeScript plugins that aim to improve your experience when using Nuxt-specific features:
Note
Read more in the documentation.
To enable this feature, set
experimental.typescriptPlugintotruein your Nuxt configuration:export default defineNuxtConfig({ experimental: { typescriptPlugin: true } })Once enabled, the module will be automatically installed and configured by Nuxt.
Important
This feature also requires selecting the workspace TypeScript version in VS Code. Run the "TypeScript: Select TypeScript Version" command and choose "Use Workspace Version".
Other Improvements
Component
declarationPath– You can now specify a custom declaration path for components
Important Fixes
Route hash is now preserved when redirecting based on
routeRulesFixed concurrent calls to
loadNuxtConfigwith proper cleanupObject-format
hrefnow works correctly in<NuxtLink>Component auto-imports now work as arguments to Vue's
h()functionFixed app config array handling during HMR
Upgrading
Our recommendation for upgrading is to run:
npx nuxt upgrade --dedupe
This will refresh your lockfile and pull in all the latest dependencies that Nuxt relies on, especially from the unjs ecosystem.
Changelog
Performance
kit,schema: Remove some unnecessary dependencies
Fixes
nuxt: Remove
mergeModelsfrom auto imports- Removed
nuxt: Remove
declarationPathfrom component dirs webpack,rspack: Preserve prerender + nitro flags in server builds
Refactors
- Deprecated
schema: Deprecate
extend,extendConfig, andconfigResolvedhooks
Documentation
- Removed
Remove deprecated node version
4.1.3
6 Oct 2025Our recommendation for upgrading is to run:
4.1.3 is a regularly scheduled patch release.
Upgrading
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.
Changelog
4.1.2
12 Sep 2025nuxt: Remove watcher from
hydrate-whenlazy hydration strategynuxt: Remove unused
enabledfrom components dir options
4.1.2 is a regularly scheduled patch release.
Upgrading
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.
Changelog
Performance
nuxt: Remove watcher from
hydrate-whenlazy hydration strategy
Fixes
nuxt: Remove unused
enabledfrom components dir options
4.1.1
5 Sep 2025- Removed
vite: Remove explicit vite-node configuration of
deps.inline nuxt: Correct relative path of auto imported components
nuxt: Prefer accessing
globalThisoverwindow
v4.1.1 is a regularly scheduled patch release
Upgrading
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.
Changelog
Fixes
nuxt: Correct relative path of auto imported components
nuxt: Prefer accessing
globalThisoverwindownuxt: Migrate to AST-aware tree-shaking + route injection
nuxt: Ignore #components import mapping inside packages that use it internally
- Removed
vite: Remove explicit vite-node configuration of
deps.inline nuxt: Include trace in dev-time
useRouteusage warningkit: Improve DX by displaying module name when possible
nuxt: Print route middleware path in warning
nuxt: Include core auto-imports from
imports:sourcesin override warningnuxt: Render relative importmap entry path if required
4.1.0
2 Sep 2025A component is changed slightly - the hash of its JS chunk changes
The page which uses the component has to be updated to reference the new file name
The entry now has its hash changed because it dynamically imports the page
Highlights
Build and Performance Improvements
Enhanced Chunk Stability
Build stability has been significantly improved with import maps (#33075). This prevents cascading hash changes that could invalidate large portions of your build when small changes are made:
<!-- Automatically injected import map --> <script type="importmap">{"imports":{"#entry":"/_nuxt/DC5HVSK5.js"}}</script>By default, JS chunks emitted in a Vite build are hashed, which means they can be cached immutably. However, this can cause a significant issue: a change to a single component can cause every hash to be invalidated, massively increasing the chance of 404s.
In short:
A component is changed slightly - the hash of its JS chunk changes
The page which uses the component has to be updated to reference the new file name
The entry now has its hash changed because it dynamically imports the page
every other file which imports the entry has its hash changed because the entry file name is changed
Obviously this wasn't optimal. With this new feature, the hash of (otherwise) unchanged files which import the entry won't be affected.
This feature is automatically enabled and helps maintain better cache efficiency in production. It does require native import map support, but Nuxt will automatically disable it if you have configured
vite.build.targetto include a browser that doesn't support import maps.And of course you can disable it if needed:
export default defineNuxtConfig({ experimental: { entryImportMap: false } })Experimental Rolldown Support
Nuxt now includes experimental support for
rolldown-vite(#31812), bringing Rust-powered bundling for potentially faster builds.To try Rolldown in your Nuxt project, you need to override Vite with the rolldown-powered version since Vite is a dependency of Nuxt. Add the following to your
package.json:npm:
{ "overrides": { "vite": "npm:rolldown-vite@latest" } }pnpm:
{ "pnpm": { "overrides": { "vite": "npm:rolldown-vite@latest" } } }yarn:
{ "resolutions": { "vite": "npm:rolldown-vite@latest" } }bun:
{ "overrides": { "vite": "npm:rolldown-vite@latest" } }After adding the override, reinstall your dependencies. Nuxt will automatically detect when Rolldown is available and adjust its build configuration accordingly.
For more details on Rolldown integration, see the Vite Rolldown guide.
Note
This is experimental and may have some limitations, but offers a glimpse into the future of high-performance bundling in Nuxt.
Improved Lazy Hydration
Lazy hydration macros now work without auto-imports (#33037), making them more reliable when component auto-discovery is disabled:
<script setup> // Works even with components: false const LazyComponent = defineLazyHydrationComponent( 'visible', () => import('./MyComponent.vue') ) </script>This ensures that components that are not "discovered" through Nuxt (e.g., because
componentsis set tofalsein the config) can still be used in lazy hydration macros.Enhanced Page Rules
If you have enabled experimental extraction of route rules, these are now exposed on a dedicated
rulesproperty onNuxtPageobjects (#32897), making them more accessible to modules and improving the overall architecture:// In your module nuxt.hook('pages:extend', pages => { pages.push({ path: '/api-docs', rules: { prerender: true, cors: true, headers: { 'Cache-Control': 's-maxage=31536000' } } }) })The
defineRouteRulesfunction continues to work exactly as before, but now provides better integration possibilities for modules.Module Development Enhancements
Module Dependencies and Integration
Modules can now specify dependencies and modify options for other modules (#33063). This enables better module integration and ensures proper setup order:
export default defineNuxtModule({ meta: { name: 'my-module', }, moduleDependencies: { 'some-module': { // You can specify a version constraint for the module version: '>=2', // By default moduleDependencies will be added to the list of modules // to be installed by Nuxt unless `optional` is set. optional: true, // Any configuration that should override `nuxt.options`. overrides: {}, // Any configuration that should be set. It will override module defaults but // will not override any configuration set in `nuxt.options`. defaults: {} } }, setup (options, nuxt) { // Your module setup logic } })This replaces the deprecated
installModulefunction and provides a more robust way to handle module dependencies with version constraints and configuration merging.Module Lifecycle Hooks
Module authors now have access to two new lifecycle hooks:
onInstallandonUpgrade(#32397). These hooks allow modules to perform additional setup steps when first installed or when upgraded to a new version:export default defineNuxtModule({ meta: { name: 'my-module', version: '1.0.0', }, onInstall(nuxt) { // This will be run when the module is first installed console.log('Setting up my-module for the first time!') }, onUpgrade(inlineOptions, nuxt, previousVersion) { // This will be run when the module is upgraded console.log(`Upgrading my-module from v${previousVersion}`) } })The hooks are only triggered when both
nameandversionare provided in the module metadata. Nuxt uses the.nuxtrcfile internally to track module versions and trigger the appropriate hooks. (If you haven't come across it before, the.nuxtrcfile should be committed to version control.)Tip
This means module authors can begin implementing their own 'setup wizards' to provide a better experience when some setup is required after installing a module.
Enhanced File Resolution
The new
ignoreoption forresolveFiles(#32858) allows module authors to exclude specific files based on glob patterns:// Resolve all .vue files except test files const files = await resolveFiles(srcDir, '**/*.vue', { ignore: ['**/*.test.vue', '**/__tests__/**'] })Layer Directories Utility
A new
getLayerDirectoriesutility (#33098) provides a clean interface for accessing layer directories without directly accessing private APIs:import { getLayerDirectories } from '@nuxt/kit' const layerDirs = await getLayerDirectories(nuxt) // Access key directories: // layerDirs.app - /app/ by default // layerDirs.appPages - /app/pages by default // layerDirs.server - /server by default // layerDirs.public - /public by defaultDeveloper Experience Improvements
Simplified Kit Utilities
Several kit utilities have been improved for better developer experience:
addServerImportsnow supports single imports (#32289):
// Before: required array addServerImports([{ from: 'my-package', name: 'myUtility' }]) // Now: can pass directly addServerImports({ from: 'my-package', name: 'myUtility' })Performance Optimizations
This release includes several internal performance optimizations:
Improved route rules cache management
Optimized app manifest watching
Better TypeScript processing for page metadata
Notable Fixes
Improved
useFetchhook typingBetter handling of TypeScript expressions in page metadata (#32902, #32914)
Enhanced route matching and synchronization
Reduced verbosity of Vue server warnings in development
Better handling of relative time calculations in
<NuxtTime>
Upgrading
As usual, our recommendation for upgrading is to run:
npx nuxt upgrade --dedupe
This will refresh your lockfile and pull in all the latest dependencies that Nuxt relies on, especially from the unjs ecosystem.
Changelog
Enhancements
kit: Add
ignoreoption toresolveFileskit: Add
onInstallandonUpgrademodule hooksnuxt,vite: Add experimental support for
rolldown-vitenuxt: Extract
defineRouteRulesto pagerulespropertynuxt,vite: Use importmap to increase chunk stability
nuxt: Lazy hydration macros without auto-imports
kit,nuxt,schema: Allow modules to specify dependencies
kit,nuxt: Add
getLayerDirectoriesutil and refactor to use it
Performance
nuxt: Clear inline route rules cache when pages change
nuxt: Stop watching app manifest once a change has been detected
Fixes
nuxt: Handle
satisfiesin page augmentationnuxt: Type response in
useFetchhooksnuxt: Add TS parenthesis and as expression for page meta extraction
nuxt: Use correct unit thresholds for relative time
nuxt: Handle uncached current build manifests
kit: Resolve directories in
resolvePathand normalize file extensionsschema,vite: Bump
requestTimeout+ allow configurationnuxt: Deep merge extracted route meta
nuxt: Do not expose app components until fully resolved
kit: Only exclude
node_modules/if no customsrcDirnuxt: Transform ts before page meta extraction
nuxt: Compare final matched routes when syncing
routeobjectnuxt: Make vue server warnings much less verbose in dev mode
schema: Allow disabling cssnano/autoprefixer postcss plugins
kit: Ensure local layers are prioritised alphabetically
kit,nuxt: Expose global types to vue compiler
deps: Bump devalue
nuxt: Support config type inference for
defineNuxtModule().with()nuxt: Search for colliding names in route children
nuxt: Delete
nuxtApp._runningTransitionon resolvenuxt: Add validation for nuxt island reviver key
4.0.3
5 Aug 2025kit: Get absolute path from
tinyglobbyinresolveFilesnuxt: Do not throw undefined
errorvariablevite: Include tsconfig references during
typeCheck
4.0.3 is a regularly scheduled patch release.
Changelog
Performance
kit: Get absolute path from
tinyglobbyinresolveFiles
Fixes
nuxt: Do not throw undefined
errorvariablevite: Include tsconfig references during
typeChecknuxt: Add sourcemap path transformation for client builds
nuxt: Add warning for lazy-hydration missing prefix
nuxt: Trigger call once navigation even when no suspense
webpack: Handle
nullresult from webpack callkit,nuxt: Use
reverseResolveAliasfor better errors
4.0.2
29 Jul 2025nuxt: Provide typed slots for
<ClientOnly>and<DevOnly>kit,nuxt,schema: Add trailing slash to some dir aliases
nuxt: Constrain global
defineAppConfigtype
4.0.2 is the next patch release.
Timetable: 28 July.
Changelog
Fixes
nuxt: Provide typed slots for
<ClientOnly>and<DevOnly>kit,nuxt,schema: Add trailing slash to some dir aliases
nuxt: Constrain global
defineAppConfigtypekit: Include module types in
appcontextnuxt: Include source base url for remote islands
vite: Use vite node server to transform requests
kit: Use
mllyto parse module pathsnuxt: Execute all plugins after error rendering error.vue
4.0.1
21 Jul 2025nuxt: Add
nuxt.schemafiles to node tsconfig contextnuxt,vite: Unpin
nitropacknuxt: Expose shared aliases within
shared/dir
v4.0.1 is the first regularly scheduled patch release of v4
It will be followed up later this week with v3.18, which will backport a number of the features/fixes from Nuxt v4 to v3.
Upgrading
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.
Changelog
Fixes
nuxt: Add
nuxt.schemafiles to node tsconfig contextnuxt,vite: Unpin
nitropacknuxt: Expose shared aliases within
shared/dir
4.0.0
15 Jul 2025- Breaking
nuxt: ⚠️ Remove old experimental options
- Breaking
kit: ⚠️ Support loading nuxt 4 and drop support for <=2
- Breaking
nuxt: ⚠️ Remove
__NUXT__after hydration
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:
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
useAsyncDataanduseFetchwork 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.jsonfile 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.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
deps: Upgrade to latest versions of c12, jiti and unbuild
Fixes
nuxt: ⚠️ Remove old experimental options
kit: ⚠️ Support loading nuxt 4 and drop support for <=2
nuxt: ⚠️ Remove
__NUXT__after hydrationkit: ⚠️ Drop support for building nuxt 2 projects
nuxt: ⚠️ Remove unused
globalNamepropertykit,nuxt,schema: ⚠️ Remove other support for nuxt2/bridge
nuxt: Remove unneeded subpath import
nuxt,schema: ⚠️ Remove support for
compatibilityVersion: 3kit,nuxt,schema,vite: ⚠️ Remove support for some deprecated options
nuxt: ⚠️ Remove public and assets aliases
schema: ⚠️ Remove top level generate option
deps: Upgrade to rc version of
@nuxt/cli
CI
Breaking Changes
- 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: ⚠️ Remove unused
globalNameproperty - Breaking
kit,nuxt,schema: ⚠️ Remove other support for nuxt2/bridge
- Breaking
nuxt,schema: ⚠️ Remove support for
compatibilityVersion: 3 - Breaking
kit,nuxt,schema,vite: ⚠️ Remove support for some deprecated options
- Breaking
nuxt: ⚠️ Remove public and assets aliases
- Breaking
schema: ⚠️ Remove top level generate option
- Breaking
kit,nuxt,vite,webpack: ⚠️ Remove legacy require utils
- Breaking
schema: ⚠️ Remove config.schema.json export + defaults
- 3.x
3.21.11
5 Aug 20263.21.11 is a patch release.
Important
Nuxt v3 is now end-of-life. Please upgrade to Nuxt v4, or you may wish to check out our partner HeroDevs who provide never-ending support for end-of-life releases
Changelog
3.21.10
27 Jul 2026rspack,webpack: Resolve loaders and runtime deps from nuxt dirs
nuxt: Remove dev error overlay when error is cleared
rspack,webpack: Resolve bundled postcss defaults from builder
⚠️ This is a security release. We recommend upgrading as soon as possible with
npx nuxt upgrade --dedupe.It fixes server-side RCE and unauthorized component instantiation via server island props, a route rule authorization bypass, server component DoS, and dev server path disclosure. Refreshing your lockfile also pulls in
@nuxt/devtools@3.3.1, which fixes a separate critical development-only RCE.If you already upgraded for the earlier route rule advisory (CVE-2026-53721), you still need this release: one of the fixes addresses a regression introduced by that fix.
Full details: Nuxt Security Patch Releases and GitHub Security Advisories.
Changelog
Fixes
rspack,webpack: Resolve loaders and runtime deps from nuxt dirs
nuxt: Remove dev error overlay when error is cleared
rspack,webpack: Resolve bundled postcss defaults from builder
3.21.9
18 Jul 2026rspack,webpack: Strip invalid webpack PURE annotations
3.21.9 is the next patch release.
Changelog
Fixes
rspack,webpack: Strip invalid webpack PURE annotations
3.21.8
8 Jun 2026vite: Shorter socket name for macOs with tmp fallback
kit: Respect
typeoption infindPathdeps: Update nuxt/scripts presets
3.21.8 is a hotfix release to address an issue running the dev server on MacOS.
Changelog
Fixes
vite: Shorter socket name for macOs with tmp fallback
kit: Respect
typeoption infindPathdeps: Update nuxt/scripts presets
3.21.7
2 Jun 2026rspack,webpack: Require loopback host when missing same-origin signals
3.21.7 is the a security hotfix release.
👉 make sure to check github.com/nuxt/nuxt/security/advisories to view open advisories resolved by this release.
Changelog
Fixes
rspack,webpack: Require loopback host when missing same-origin signals
3.21.6
18 May 20263.21.5
10 May 2026nitro: Remove unused middleware
3.21.1
7 Feb 2026Only enable dynamic imports when ts plugin
3.21.1 is a regularly schedule patch release.
Changelog
Fixes
Only enable dynamic imports when ts plugin
3.21.0
22 Jan 2026- Removed
Remove babel debugging plugin from jiti stub options
Continue making pull requests to the
mainbranchWe'll backport changes to the
4.xand3.xbranches
3.21.0 is the next minor release.
Nuxt 4.3 and 3.21 bring powerful new features for layouts, caching, and developer experience – plus significant performance improvements under the hood.
Some News
Extended v3 Support
Early this month, I opened a discussion to find out how the upgrade had gone from v3 to v4. I was really pleased to hear how well it had gone for most people.
Having said that, we're committed to making sure no one gets left behind. And so we will continue to provide security updates and critical bug fix releases beyond the previously announced end-of-life date of January 31, 2026, meaning Nuxt v3 will meet its end-of-life on July 31, 2026.
Tip
As usual, today also brings a minor release for v3, with many of the same improvements backported from v4.3.
Preparing for Nuxt 5
We're closer than ever to the releases of Nuxt v5 and Nitro v3. In the coming weeks, the
mainbranch of the Nuxt repository will begin receiving initial commits for Nuxt 5. However, it's still business as usual.Continue making pull requests to the
mainbranchWe'll backport changes to the
4.xand3.xbranches
Keep an eye out on the Upgrade Guide – we'll be adding details about how you can already start migrating your projects to prepare for Nuxt v4 with
future.compatibilityVersion: 5.Route Rule Layouts
But that's enough about the future. We have a lot of good things for you today!
First, you can now set layouts directly in route rules using the new
appLayoutproperty (#31092). This provides a centralized, declarative way to manage layouts across your application without scatteringdefinePageMetacalls throughout your pages.export default defineNuxtConfig({ routeRules: { '/admin/**': { appLayout: 'admin' }, '/dashboard/**': { appLayout: 'dashboard' }, '/auth/**': { appLayout: 'minimal' } } })This might be useful for:
Admin panels with a shared layout across many routes
Marketing pages that need a different layout from the app
Tip
Plus, you can pass props to layouts now! See the
setPageLayoutimprovements below.ISR/SWR Payload Extraction
Payload extraction now works with ISR (incremental static regeneration), SWR (stale-while-revalidate) and cache
routeRules(#33467). Previously, only pre-rendered pages could generate_payload.jsonfiles.This means:
Client-side navigation to ISR/SWR pages can use cached payloads
CDNs (Vercel, Netlify, Cloudflare) can cache payload files alongside HTML
Fewer API calls during navigation – data can be prefetched and served from the cached payload
export default defineNuxtConfig({ routeRules: { '/products/**': { isr: 3600, // Revalidate every hour } } })Dev Mode Payload Extraction
Related to the above, payload extraction now also works in development mode (#30784). This makes it easier to test and debug payload behavior without needing to run a production build.
Important
Payload extraction works in dev mode with
nitro.staticset totrue, or for individual pages which haveisr,swr,prerenderorcacheroute rules.Disable Modules from Layers
When extending Nuxt layers, you can now disable specific modules that you don't need (#33883). Just pass
falseto the module's options:export default defineNuxtConfig({ extends: ['../shared-layer'], // disable @nuxt/image from layer image: false, })Route Groups in Page Meta
Route groups (folders wrapped in parentheses like
(protected)/) are now exposed in page meta (#33460). This makes it easy to check which groups a route belongs to in middleware or anywhere you have access to the route.<script setup lang="ts"> // This page's meta will include: { groups: ['protected'] } useRoute().meta.groups </script>export default defineNuxtRouteMiddleware((to) => { if (to.meta.groups?.includes('protected') && !isAuthenticated()) { return navigateTo('/login') } })This provides a clean, convention-based approach to route-level authorization without needing to add
definePageMetato every protected page.Layout Props with
setPageLayoutThe
setPageLayoutcomposable now accepts a second parameter to pass props to your layout (#33805):export default defineNuxtRouteMiddleware((to) => { setPageLayout('admin', { sidebar: true, theme: 'dark' }) })<script setup lang="ts"> defineProps<{ sidebar?: boolean theme?: 'light' | 'dark' }>() </script>#serverAliasA new
#serveralias provides clean imports within your server directory (#33870), similar to how#sharedworks:// Before: relative path hell import { helper } from '../../../../utils/helper' // After: clean and predictable import { helper } from '#server/utils/helper'The alias includes import protection – you can't accidentally import
#servercode from client or shared contexts.Draggable Error Overlay
The development error overlay introduced in Nuxt 4.2 is now draggable and can be minimized (#33695). You can:
Drag it to any corner of the screen (it snaps to edges)
Minimize it to a small pill button when you want to keep working
Your position and minimized state persist across page reloads
This is a quality-of-life improvement when you're iterating on fixes and don't want the overlay blocking your view.
github.com/user-attachments/assets/nuxt_4-3_err…
Async Plugin Constructors
Module authors can now use async functions when adding build plugins (#33619):
export default defineNuxtModule({ async setup() { // Lazy load only when actually needed addVitePlugin(() => import('my-cool-plugin').then(r => r.default())) // No need to load webpack plugin if using Vite addWebpackPlugin(() => import('my-cool-plugin/webpack').then(r => r.default())) } })This enables true lazy loading of build plugins, avoiding unnecessary code loading when plugins aren't needed.
Performance Improvements
This release includes several performance optimizations for faster builds:
Hook filters - Internal plugins now use filters to avoid running hooks unnecessarily
SSR styles optimization - The
nuxt:ssr-stylesplugin is now significantly faster (#33862, #33865)Layer alias transform - Skipped when using Vite (it handles this natively)
Route rules compilation - Route rules are now compiled into a client chunk using
rou3, removing the need forradix3in the client bundle and eliminating app manifest fetches
Inline Styles for Webpack/Rspack
The
inlineStylesfeature now works with webpack and rspack builders (#33966), not just Vite. This enables critical CSS inlining for better Core Web Vitals regardless of your bundler choice.Deprecations
statusCode→status,statusMessage→statusTextIn preparation for Nitro v3 and H3 v2, we're moving to use Web API naming conventions (#33912). The old properties still work but are deprecated in advance of v5:
- throw createError({ statusCode: 404, statusMessage: 'Not Found' }) + throw createError({ status: 404, statusText: 'Not Found' })Bug Fixes
Notable fixes in this release:
Fixed head component deduplication using
keyattribute (#33958, #33963)Fixed async data properties not being reactive in Options API
Fixed
useCookieunsafe number parsing during decodeFixed
NuxtPagenot re-rendering when nestedNuxtLayouthas layouts disabledFixed client-side pathname decoding for non-ASCII route aliases
Fixed suspense remounting when navigating after pending state
Fixed clipboard copy in error overlay
Enabled
allowArbitraryExtensionsby default in TypeScript configAdded
noUncheckedIndexedAccessto server tsconfig for safer typing
Important
Enabling
noUncheckedIndexedAccessin the Nitro server TypeScript config improves type safety but may surface new type errors in your server code. This change was necessary because Nuxt's app context performs type checks on server routes (learn more).While we recommend keeping this enabled for better type safety, you can disable it if needed:
export default defineNuxtConfig({ nitro: { typescript: { tsConfig: { compilerOptions: { noUncheckedIndexedAccess: false } } } } })Note that disabling this may allow type errors to slip through that could cause runtime issues with indexed access.
Nuxt 3.21.0
Alongside v4.3.0, we're releasing Nuxt v3.21.0 with many of the same improvements backported to the 3.x branch. This release includes:
All the same features: Route rule layouts, ISR payload extraction, layout props with
setPageLayout,#serveralias, draggable error overlay, and moreAll performance improvements: SSR styles optimization, hook filters, and route rules compilation
Module disabling: Disable layer modules by setting options to
falseCritical bug fixes: Async data reactivity in Options API,
useCookienumber parsing, head component deduplication, and more
Upgrading
Our recommendation for upgrading is to run:
npx nuxt@latest upgrade --dedupe --channel=v3
This will deduplicate your lockfile and help ensure you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
Tip
Check out our upgrade guide if upgrading from an older version.
Changelog
Enhancements
kit: Support async constructor for adding plugins
kit: Export Nuxt major version type
schema: Add
#serveralias for server directory importsschema: Hoist nitro
crosswstypesnitro,nuxt: Compile route rules into client chunk
nuxt: Allow disabling modules by setting module options to
falsekit: Allow specifying
moduleDependenciesas an async functionnuxt: Support
appLayoutin route rulesnuxt: Add route groups to page meta
nuxt: Enable payload extraction for ISR/SWR routes
nuxt: Allow updating props with
setPageLayoutnuxt: Enable dragging and minimizing for error overlay
nitro,nuxt: Add support for payload extraction in dev
rspack,webpack: Add inline styles
kit: Add forward-compatible nitro types
Performance
nuxt: Do not init layer alias transform when using vite
vite: Add hook filters for ssr styles plugin
vite: Optimize
nuxt:ssr-stylespluginnuxt: Use filter for vfs plugin load
nuxt,vite: Use filters to avoid running hooks unnecessarily
nuxt,vite: Add more filters to internal plugins
Fixes
kit: Normalize local layer paths with trailing slashes
nuxt: Avoid overwriting multiple head input in island handler
nuxt: Update meta instead of calling
router.replacein page hmrnuxt: Don't call
page:loading:endin cache if already calledvite: Add error handling for parsing
NUXT_VITE_NODE_OPTIONSnuxt: Do not skip middleware when
appMiddlewarereferences invalid keynitro: Clipboard copy in error overlay
webpack,rspack: Resolve deep imports in virtual files
webpack: Disable async chunks in dev mode
webpack: Correctly evaluate sourcemap name
nuxt: Handle node10 resolution for
nuxt/metanuxt: Do not early return if component priorities conflict
nuxt: Use
keyfor tag deduplication in<Head>componentschema,vite: Resolve
build.transpilewhen initialising vitenuxt,rspack,webpack: Inject module identifiers for webpack builders
nuxt: Add key to head components for proper deduplication
nitro: Check prettyResponse.body type before error overlay
nuxt: Don't URI-encode static route paths
nuxt: Skip internal stub routes from prerender
kit,schema: Align module
onUpgradearguments with typesnuxt: Handle unsafe number parsing in useCookie decode
nuxt: Do not externalise
rou3nitro: Add
noUncheckedIndexedAccessto server tsconfignuxt: Update global reference to globalThis in
useRequestFetchvite: Configure hmr port for server build
kit: Add forward compatible nitro v3 types
nitro,nuxt: Do not import nitro deps in builders
nitro: Add
h3types to auto-importsschema: Add some more directories to ignore
nitro: Also augment
nuxt/schemanuxt: Make asyncData properties reactive in Options API
nuxt: Rerender
NuxtPagewhen nestedNuxtLayouthas explicitly disabled layoutsnuxt,schema: Clean up types
nuxt: Allow user augmentation of runtime config
kit,nitro: Enable
allowArbitraryExtensionsby defaultnuxt: Decode client-side pathname for non-ASCII route aliases
nuxt: Force remount suspense when navigating after pending
nuxt: Add documentation link to server builder error message
nuxt: Validate placeholder/fallback tags + warn about placeholder/fallback props
nuxt: Force flush
useAsyncDatadebounced execute post watcher flushnitro: Process isr/swr/cache keys
nuxt: Add
typeFromsupport forimports.d.tstemplate exportsnuxt: Ensure we inline styles for
hydrate-nevercomponents
Build
- Removed
Remove babel debugging plugin from jiti stub options
3.20.2
9 Dec 2025nitro: Do not show pretty error handler when testing
nuxt: Generate valid references for component declaration items
nuxt: Sync internal route before calling
page:finishhook
3.20.2 is the next patch release.
Upgrading
Our recommendation for upgrading is to run:
npx nuxt upgrade --dedupe --channel=v3
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.
Note
This will only work if you already have a version of
@nuxt/cliwhich has the--channelflag. If this does not work, you can instead runnpx nuxi@latestfor the initial upgrade.Changelog
Fixes
nitro: Do not show pretty error handler when testing
nuxt: Generate valid references for component declaration items
nuxt: Sync internal route before calling
page:finishhooknitro: Ensure html is a string before injecting error handler
nitro: Include layer server directories in
tsconfig.server.jsonnuxt: Ensure deduped async data executions return latest promise
kit,nuxt: Type + respect
moduleDependenciesby meta namenuxt,schema: Ignore
.d.vue.tsdeclarationskit,nuxt: Protect against resolved nuxt module subpath
nuxt: Re-execute
callOnceduring HMRnuxt: Resolve watch callback after reactive key change in
useAsyncDatanuxt: Escape HTML in development error page stack trace
kit: Do not add resolved
rootDirto cached layer configkit,schema: Add
moduleDependencies->installModule
3.20.1
6 Nov 2025- Deprecated
kit,nuxt,schema: Deprecate
ImportPresetWithDeprecation vite: Unset
optimizeDeps.includefor server environmentnuxt: Correct warning message for prefetch/noPrefetch conflict
3.20.1 is the next patch release.
Upgrading
Our recommendation for upgrading is to run:
npx nuxt upgrade --dedupe --channel=v3
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.
Changelog
Fixes
vite: Unset
optimizeDeps.includefor server environment- Deprecated
kit,nuxt,schema: Deprecate
ImportPresetWithDeprecation nuxt: Correct warning message for prefetch/noPrefetch conflict
nitro: Remove
<nuxt-error-overlay>iframe bordervite: Use rolldown replace only in build
nitro: Use directory paths in
moduleEntryPathsnitro: Start error overlay minimized based on status code
vite: Ensure
optimizeDepsconfig is applied before other pluginsnuxt: Respect layer priority order for scanned components
nuxt: Process prerender routes on
pages:resolvednuxt: Remove abort signal event listeners after render
nuxt: Cleanup event listener with cleanup signal
vite: Respect vite proxy in dev middleware
3.20.0
28 Oct 2025- Removed
nuxt: Remove
declarationPathfrom component dirs - Deprecated
schema: Deprecate
extend,extendConfig, andconfigResolvedhooks - Removed
Remove deprecated node version
3.20.0 is the next minor release.
Upgrading
Our recommendation for upgrading is to run:
npx nuxt upgrade --dedupe --channel=v3
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.
Changelog
Performance
kit,schema: Remove some unnecessary dependencies
Fixes
nuxt: Remove
mergeModelsfrom auto imports- Removed
nuxt: Remove
declarationPathfrom component dirs webpack,rspack: Preserve prerender + nitro flags in server builds
Refactors
- Deprecated
schema: Deprecate
extend,extendConfig, andconfigResolvedhooks
Documentation
- Removed
Remove deprecated node version
3.19.3
6 Oct 2025Our recommendation for upgrading is to run:
3.19.3 is a regularly scheduled patch release.
Upgrading
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.
Changelog
3.19.2
12 Sep 2025nuxt: Remove watcher from
hydrate-whenlazy hydration strategynuxt: Remove unused
enabledfrom components dir options
3.19.2 is a regularly scheduled patch release.
Upgrading
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.
Changelog
Performance
nuxt: Remove watcher from
hydrate-whenlazy hydration strategy
Fixes
nuxt: Remove unused
enabledfrom components dir options
3.19.1
5 Sep 2025- Removed
vite: Remove explicit vite-node configuration of
deps.inline nuxt: Correct relative path of auto imported components
nuxt: Prefer accessing
globalThisoverwindow
v3.19.1 is a regularly scheduled patch release
Upgrading
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.
Changelog
Fixes
nuxt: Correct relative path of auto imported components
nuxt: Prefer accessing
globalThisoverwindownuxt: Migrate to AST-aware tree-shaking + route injection
nuxt: Ignore #components import mapping inside packages that use it internally
- Removed
vite: Remove explicit vite-node configuration of
deps.inline nuxt: Include trace in dev-time
useRouteusage warningnuxt: Print route middleware path in warning
nuxt: Include core auto-imports from
imports:sourcesin override warningnuxt: Render relative importmap entry path if required
3.19.0
2 Sep 2025kit: Add
ignoreoption toresolveFileskit: Add
onInstallandonUpgrademodule hooksnuxt,vite: Add experimental support for
rolldown-vite
Highlights
Please see the release notes for Nuxt v4.1 for full details on the features and fixes in Nuxt v3.19.
Upgrading
As usual, our recommendation for upgrading is to run:
npx nuxt upgrade --dedupe
This will refresh your lockfile and pull in all the latest dependencies that Nuxt relies on, especially from the unjs ecosystem.
Changelog
Enhancements
kit: Add
ignoreoption toresolveFileskit: Add
onInstallandonUpgrademodule hooksnuxt,vite: Add experimental support for
rolldown-vitenuxt: Extract
defineRouteRulesto pagerulespropertynuxt,vite: Use importmap to increase chunk stability
nuxt: Lazy hydration macros without auto-imports
kit,nuxt,schema: Allow modules to specify dependencies
kit,nuxt: Add
getLayerDirectoriesutil and refactor to use it
Performance
nuxt: Clear inline route rules cache when pages change
nuxt: Stop watching app manifest once a change has been detected
Fixes
nuxt: Handle
satisfiesin page augmentationnuxt: Type response in
useFetchhooksnuxt: Add TS parenthesis and as expression for page meta extraction
nuxt: Use correct unit thresholds for relative time
nuxt: Handle uncached current build manifests
kit: Resolve directories in
resolvePathand normalize file extensionsschema,vite: Bump
requestTimeout+ allow configurationnuxt: Deep merge extracted route meta
nuxt: Do not expose app components until fully resolved
kit: Only exclude
node_modules/if no customsrcDirnuxt: Compare final matched routes when syncing
routeobjectnuxt: Make vue server warnings much less verbose in dev mode
schema: Allow disabling cssnano/autoprefixer postcss plugins
kit: Ensure local layers are prioritised alphabetically
kit,nuxt: Expose global types to vue compiler
nuxt: Support config type inference for
defineNuxtModule().with()nuxt: Search for colliding names in route children
nuxt: Delete
nuxtApp._runningTransitionon resolvenuxt: Add validation for nuxt island reviver key
kit: Prioritise local layers over extended layers
kit: Address merge conflict
kit: Do not resolve public dir aliases
3.18.1
5 Aug 2025kit: Get absolute path from
tinyglobbyinresolveFilesnuxt: Do not throw undefined
errorvariablevite: Include tsconfig references during
typeCheck
3.18.1 is a regularly scheduled patch release.
Changelog
Performance
kit: Get absolute path from
tinyglobbyinresolveFiles
Fixes
nuxt: Do not throw undefined
errorvariablevite: Include tsconfig references during
typeChecknuxt: Add sourcemap path transformation for client builds
nuxt: Add warning for lazy-hydration missing prefix
nuxt: Trigger call once navigation even when no suspense
webpack: Handle
nullresult from webpack callkit,nuxt: Use
reverseResolveAliasfor better errors
3.18.0
29 Jul 2025Typed slots for
<ClientOnly>and<DevOnly>(#32707) - better IntelliSense and error checkingExported
<NuxtTime>prop types (#32547) - easier to extend and customizeImproved Vite-node communication via internal socket (#32417) for faster development builds
3.18.0 is the next minor release.
Highlights
A huge thank you to everyone who's been a part of this release, which is mostly about backporting features + bugfixes from Nuxt v4.
Over the next six months, we'll continue backporting compatible v4 features and bug fixes, so please keep the feedback coming! ❤️
Lazy Hydration Macros
Building on the delayed hydration support from v3.16, we now support lazy hydration macros (#31192)! These provide a more ergonomic way to control component hydration:
<script setup lang="ts"> const LazyHydrationMyComponent = defineLazyHydrationComponent( 'visible', () => import('./components/MyComponent.vue') ) </script> <template> <div> <!-- Hydration will be triggered when the element(s) is 100px away from entering the viewport. --> <LazyHydrationMyComponent :hydrate-on-visible="{ rootMargin: '100px' }" /> </div> </template>These macros make it possible to use Nuxt's lazy hydration utilities alongside explicit component imports.
Accessibility Improvements
We've enhanced accessibility by including
<NuxtRouteAnnouncer>in the built-inapp.vue(#32621). This means page changes will be announced to screen readers, making navigation more accessible for users with visual impairments. (This only applies if you do not have anapp.vuein your project. If you do, please keep<NuxtRouteAnnouncer>in yourapp.vue!)Enhanced Development Experience
Chrome DevTools Workspace Integration
We've added Chrome DevTools workspace integration (#32084), allowing you to edit your Nuxt source files directly from Chrome DevTools. This creates a better debugging experience where changes made in DevTools are reflected in your actual source files.
Better Component Type Safety
Component type safety has been improved with:
Typed slots for
<ClientOnly>and<DevOnly>(#32707) - better IntelliSense and error checkingExported
<NuxtTime>prop types (#32547) - easier to extend and customize
New Auto-Import:
onWatcherCleanupThe
onWatcherCleanupfunction fromvueis now available as an auto-import (#32396), making it easier to clean up watchers and prevent memory leaks:const { data } = useAsyncData('users', fetchUsers) watch(data, (newData) => { const interval = setInterval(() => { // Some periodic task }, 1000) // Clean up when the watcher is stopped onWatcherCleanup(() => { clearInterval(interval) }) })Observability Enhancements
Page routes are now exposed to Nitro for observability (#32617), enabling better monitoring and analytics integration with supported platforms. This allows observability tools to track page-level metrics more effectively.
Module Development Improvements
Module authors get several quality-of-life improvements:
Simplified Server Imports
The
addServerImportskit utility now supports single imports (#32289), making it easier to add individual server utilities:// Before: had to wrap in array addServerImports([{ from: 'my-package', name: 'myUtility' }]) // Now: can pass directly addServerImports({ from: 'my-package', name: 'myUtility' })TypeScript Configuration
Modules can now add to
typescript.hoist(#32601), giving them more control over TypeScript configuration and type generation.Performance Improvements
We've made several performance optimizations:
Improved Vite-node communication via internal socket (#32417) for faster development builds
Migration to
oxc-walker(#32250) and oxc foronPrehydratetransforms (#32045) for faster code transformations
Bug Fixes
This release also includes several important fixes:
Improved data fetching: When computed keys change, old data is now properly retained
Better scroll behavior:
scrollBehaviorTypeis now only used for hash scrollingFixed directory aliases: Added trailing slashes to some directory aliases for better consistency
Upgrading
As usual, our recommendation for upgrading is to run:
npx nuxi@latest upgrade --dedupe
This refreshes your lockfile and pulls in all the latest dependencies that Nuxt relies on, especially from the unjs ecosystem.
Changelog
Enhancements
nuxt: Expose page routes to nitro for o11y
nuxt: Export
<NuxtTime>prop typesnuxt: Add integration with chrome devtools workspaces
kit: Support single import in
addServerImportsnuxt: Add
onWatcherCleanupto imports presetsnuxt: Add route announcer to default app.vue
nuxt: Support lazy hydration macros
Performance
vite: Communicate with vite-node via internal socket
kit: Update env expansion regex to match nitro
Fixes
nuxt: Allow modules to add to
typescript.hoistnuxt: Retain old data when computed key changes
nuxt: Only use
scrollBehaviorTypefor hash scrollingnuxt: Add missing
asyncnuxt: Fix transform/minify types + bump oxc-transform
nuxt: Provide typed slots for
<ClientOnly>and<DevOnly>kit,nuxt,schema: Add trailing slash to some dir aliases
nuxt: Include source base url for remote islands
vite: Use vite node server to transform requests
kit: Use
mllyto parse module pathsnuxt: Execute all plugins after error rendering error.vue
3.17.7
13 Jul 2025nuxt: Safe-guard
extraPageMetaExtractionKeysnuxt: Expose
loadBuildererror causevite: Handle resolving string vite input
3.17.7 is the last patch release before v3.18.
Upgrading
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.
Changelog
Fixes
nuxt: Safe-guard
extraPageMetaExtractionKeysnuxt: Expose
loadBuildererror causevite: Handle resolving string vite input
nuxt: Wrap only server components with island generic
vite: Ignore when client entry cannot be resolved
nuxt: Normalize segment catchall pattern before checking for parent
nuxt: Update warning message to warn against
nullvaluesnuxt: Ensure
semver.satisfiesreturns true for pre-release versionsnuxt: Scroll to anchor if present when changing page without saved position
nuxt: Handle
execute being passed towatch`
3.17.6
1 Jul 2025nuxt: Decrease if checks when prerendering
nuxt: Generate correct types for async data defaults based on
nuxt.confignuxt: Reload at base URL in
nuxt:chunk-reload-immediate
3.17.6 is a regularly scheduled patch release.
Upgrading
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.
Changelog
Performance
nuxt: Decrease if checks when prerendering
Fixes
nuxt: Generate correct types for async data defaults based on
nuxt.confignuxt: Reload at base URL in
nuxt:chunk-reload-immediatenuxt: Use rollup to calculate island component filenames
nuxt: Append
set-cookieheaders in error handlernuxt: Ensure
asyncDataruns if changing key while fetcher is runningnuxt: Handle pure hash link clicks with
navigateTonuxt: Skip external
<NuxtLink>'s custom on click handlernuxt: Update component loader regexp for minified code
nuxt: Allow camelCase for lazy hydration attributes
nuxt: Respect
inheritAttrs: falseincreateClientOnlyfnkit: Do not double-urlify file urls when resolving schema
nuxt: Align scroll behavior with page transition completion
nuxt: Set
output.generatedCode.symbolsfor nitro buildnuxt: Lazily access runtimeConfig
3.17.5
3 Jun 2025nuxt: Replace remaining instance of
globbynuxt: Export
useScriptRybbitAnalyticsfrom script stubsnuxt: Remove unneeded pattern from regexp
3.17.5 is a regularly scheduled patch release.
Upgrading
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.
Changelog
Performance
nuxt: Replace remaining instance of
globby
Fixes
nuxt: Export
useScriptRybbitAnalyticsfrom script stubsnuxt: Remove unneeded pattern from regexp
nuxt: Ensure
appConfigsources are not duplicatednuxt: Wrap slot with
h()in ClientOnlykit: Ensure template filename uses safe patterns
nuxt: Access
asyncDatastate from nuxt app instancenuxt: Make patterns relative to
srcDirinbuildCachenuxt: Return non-existent route component in RouteProvider
nuxt: Use single
asyncDatawatchervite: Use arrow functions in dynamic imports
webpack: Use plugin for rollup-compatible dynamic imports
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.