nuxt
4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed
3.21.11 is the newest release of 3.x.
In short
1 breaking1 deprecated26 new4 faster23 fixed47 internal
- Breaking
deps: ⚠️ Update dependency fork-ts-checker-webpack-plugin to v8 (main)
- Deprecated
nuxt: Deprecate scanning directory index plugins
Security
12 advisories affect 3.3.1; 4.6.0 fixes the others
- ModerateNuxt exposes the message and data of unhandled errors thrown during server renderingGHSA-96x6-fvhx-49hg · 16 Nov 2026No fix yet
- ModerateNuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routesGHSA-f3x9-2chm-73c8 · 16 Nov 2026No fix yet
- ModerateNuxt: Server-side route rules (`redirect`, `headers`, `proxy`, `ssr`) are skipped for case-variant paths when routing is case-insensitiveGHSA-vjh5-4x84-xrqp · 22 Oct 2026No fix yet
- HighNuxt: Unauthenticated CPU exhaustion parsing and hashing the Nuxt island endpoint body before hash validationGHSA-9pgf-384g-p7mv · 5 Aug 2026Fixed in 3.21.10
- HighNuxt: Unauthenticated out-of-memory crash via unbounded v-for expansion in island renderingGHSA-hxcr-hm88-mpq6 · 5 Aug 2026Fixed in 3.21.10
7 more
- HighNuxt allows DOS via cache poisoning with payload rendering responseGHSA-jvhm-gjrh-3h93 · 19 Mar 2025Fixed in 3.16.0
- ModerateNuxt: Unauthorized Component Instantiation via Server Island PropsGHSA-48hr-524c-v5w3 · 5 Aug 2026Fixed in 3.21.10
- ModerateNuxt: Reflected XSS in `<NuxtLink>` via unsanitised `javascript:` or `data:` URLGHSA-934w-87qh-qr26 · 16 Jun 2026Fixed in 3.21.7
- Moderatenuxt vulnerable to Cross-site Scripting in navigateTo if used after SSRGHSA-vf6r-87q4-2vjf · 5 Aug 2024Fixed in 3.12.4
- LowNuxt: Incomplete fix for GHSA-934w-87qh-qr26: a `javascript:` URL prefixed with an ASCII control character executes from `<NuxtLink>` when `pages` is disabledGHSA-jjm6-p2m9-9w4x · 22 Oct 2026Fixed in 4.6.0
- LowCross-site scripting via <NoScript> slot content in Nuxt's head componentsGHSA-m3q2-p4fw-w38m · 16 Jun 2026Fixed in 3.21.7
- LowNuxt: `__nuxt_island` endpoint does not bind responses to request props, enabling shared-cache poisoningGHSA-g8wj-3cr3-6w7v · 19 May 2026Fixed in 3.21.6
Release note
3.3.0 is a minor (feature) release with lots of new features to play with. 3.3.1 was a swiftly following release to patch an issue with nuxi on Windows.
Highlights
Local module development DX
We've landed a raft of changes to enable local modules and improve DX. We now auto-scan your ~/modules folder and register top level files there as modules in your project (#19394). When these files are changed, we'll automatically restart the nuxt server.
export default defineNuxtConfig({
modules: [
'@nuxtjs/tailwindcss',
- '~/modules/purge-comments'
]
})We also now expose nuxt/kit for easy access to kit composables in your local project without having to install @nuxt/kit (#19422).
Restarting Nuxt
You can add files to the watch array to automatically restart the server (#19530). This is likely to be particularly useful for module authors. You can also trigger a restart of the Nuxt server with the new restart hook (#19084). We also landed a couple of fixes on restarting the Nuxt server which should improve your experience when developing.
Performance improvements
We've increased static asset maxAge to 1yr as a matter of best practice (#19335), and support tree-shaking more of your build (#19508). We also now support preloading <NuxtLink>s with a route in object-syntax (#19120).
CleanShot 2023-03-14 at 12 19 50
We also track how long it takes each module you use to perform its setup, and warn if it takes too long. You can see all these values by running your dev server with DEBUG=1
You can also opt-in to some of Nuxt's internal optimisations by configuring composables to be treeshaken in a particular environment (#19383), or to have magic keys automatically injected (#19490) - primarily useful for module authors.
Error handling
We now handle chunk errors by default (#19086), meaning if your site updates with a redeploy, we automatically handle reloading it on navigation. You can disable this and handle it yourself with the new reloadNuxtApp composable. You can also set experimental.restoreState to preserve some of your app state across reloads.
We also have a new experimental error handling component: <NuxtClientFallback> (#8216) which can capture errors rendering on server, replace them with fallback content, and granularly trigger rerendering the part with an error on the client. This can be enabled with experimental.clientFallback - feedback very welcome!
Head improvements
We've migrated to use unhead directly (#19519) - and automatically tree-shake server-only head composables like useServerHead from your client build (#19576), meaning you can have great SEO without needing to include meta tag logic that's relevant only for crawlers in your client build.
There's also a new useHeadSafe composable that handles santising untrusted user input (#19548).
Better logging in browser DevTools
Working with the Chrome DevTools team, we've landed a couple of features across the unjs + Nuxt ecosystem meaning we now have first-class support for hiding Nuxt internal stack traces from logs in your (Chromium-based, for now) browser (#19243). We also landed a couple of improvements with stacktraces involving Nuxt hooks (#69 and #68) implementing console.createTask.
| Before | After |
|---|---|
| CleanShot 2023-03-14 at 11 55 00 | CleanShot 2023-03-14 at 11 52 27 |
Type improvements
Types for server API routes are now more correct - with non-serialisable types stripped out of the return type (#1002).
We also now type more of NuxtApp and correctly type unknown injections for greater type-safety (#19643).
CleanShot 2023-03-14 at 11 59 58
And if you were struggling with correct types when using transform + default with Nuxt data fetching composables, fear no more - we now infer the types correctly (#19487).
Nitro enhancements
This release comes with Nitro v2.3, which brings lots of improvements of its own. Check out the release for more info.
We now support useAppConfig in nitro server routes (#19489) - a long-awaited change. Now useAppConfig is consistently available throughout your app for non-runtime configuration from layers, modules, etc.
We've also added a nitro:build:public-assets hook to allow modifying assets output from nitro's prerender/build phase (#19638).
Build changes
As part of moving towards first-class support for PNP and pnpm support without --shamefully-hoist, we've dropped support for some internal (deprecated) utilities using CJS resolve patterns (#19537, #19608). We also now resolve dependencies like nuxt, @nuxt/kit and more using ESM search-paths. We'll be keeping a close eye on this.
We're also preparing the groundwork for support of new TypeScript Node16 module resolution (#19606), and as part of this have changed the format of our runtime output (using .js instead of .mjs extensions, providing types fields for subpath exports, and more).
Custom config schema (advanced)
We've been testing out an experimental feature to allow modules and users to extend the Nuxt config schema (#15592), and we've now enabled this by default (#19172). We expect this will be particularly useful for module and layer/theme authors, and should result in some nicer DX for their users.
Changelog
Enhancements
nuxi: Enforce consistent casing in filenames
nuxi: Reload nuxt when
restarthook is callednuxt: Scan composables with star export
nuxt: Add
versionsto runtime nuxtAppvite: Add
node_modulesand buildDir tox_google_ignoreListnuxi: Cli wrapper for self restart
schema: Allow adding page routes without a matching file
nuxt: Add support for
nuxt/kitsubpath for local usenuxt: Auto-register modules in
~/modulesnuxt: Enable config schema by default
kit,nuxt: Add component
priorityto allow overridingnuxt: Enable preloading object-syntax routes
nuxt: Support
trailingSlashBehaviorindefineNuxtLinknuxt: Allow configuring treeshakeable composables
nuxi,schema: Add support for setting nuxt
logLevelnuxt: Support custom keyed composables
nuxi: Programmatically pass nuxt config overrides (to dev)
vite: Use custom logger to show vite logs
nuxt: Enable chunk error handling by default
nuxt: Add
<NuxtClientFallback>componentnuxt: Add
watchoption and refactor dev server restartingnuxt: Add
useHeadSafeand remove layer around head importskit, schema: Measure module setup timings
nuxt: Support app config for server routes
nuxt: Add
nitro:build:public-assetshook
Performance
nuxt: Increase static asset maxAge to 1yr
vite: Mark more core functions as side-effect free
nuxt: Drop
@vueuse/headdependencynuxt: Tree-shake server composables + prefer server head
Fixes
nuxt: Clear loading indicator on unmount
- Deprecated
nuxt: Deprecate scanning directory index plugins
nuxt: Prevent fallthrough attributes on custom
NuxtLinkschema: Update vite
import.metatypesvite: Omit
/fromsourcemapIgnoreListfor windows supportnuxt: Pass transform options to component loader plugin
nuxi: Avoid top-level await in wrapper
nuxt: Add
kit.*files to published packagenuxt: Don't print layout warning if page is not ssr
kit: Match commit hashes of other lengths
nuxi: Handle different kind of shutdown signals
nuxt: Exclude nitro output dir from type checking
vite: Allow disabling clear screen behaviour
nuxt: Only log boot errors on client-side
nuxt: Dedupe payload cache by payload url
nuxt: Provide node16-style type exports
nuxt: Avoid injecting adhoc modules in schema
nuxt: Improve types for data fetching with
transformnuxi: Resolve kit from nuxt modules dir
nuxt,schema: Merge custom and resolved app configs
nuxt: Resolve builder using esm syntax
nuxt: Exclude
booleanfrom inline module definitionsschema: Show
payloadExtractionwarning only when unsetnuxt: Mark non-augmented NuxtApp properties as unknown
nuxt: Fix default injection type for plugins
CI
Breaking Changes
- Breaking
deps: ⚠️ Update dependency fork-ts-checker-webpack-plugin to v8 (main)
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.