Nuxt is a free and open-source framework with an intuitive and extendable way to create type-safe, performant and production-grade full-stack web applications and websites with Vue.js.
Published Node.js and peer-dependency requirements.
| Requirement | From3.21.11 on npm (opens in a new tab) | To4.0.0 on npm (opens in a new tab) |
|---|---|---|
@types/node | ^18.0.0 || ^20.0.0 || >=22.0.0Optional peer · not required | >=18.12.0Optional peer · not required |
15 Jul 2025 · Newest first
Last checked
Showing 1 of 1 releases. Full release notes.
Signals highlight changes worth reviewing. They cannot determine whether your application is affected.
nuxt: ⚠️ Remove old experimental options (#27749)
nuxt: ⚠️ Remove public and assets aliases (#32119)
schema: ⚠️ Remove top level generate option (#32355)
kit,nuxt,schema,vite: ⚠️ Remove support for some deprecated options (#32257)
kit: ⚠️ Support loading nuxt 4 and drop support for <=2 (#27837)
kit: ⚠️ Drop support for building nuxt 2 projects (1beddba6a)
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.
I'd advise reading through the upgrade guide before you start, to understand what areas of your app might be affected.
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.
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.
Nuxt 4 is all about making your development experience smoother:
app/ directory structureshared/ folder, and configurationWhy 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.
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.
Don't want to migrate? That's totally fine! Nuxt will detect your existing structure and keep working exactly as before.
Nuxt’s starter templates have an all new look, with improved accessibility, default titles, and template polish (#27843).
We've made useAsyncData and useFetch work better. Multiple components using the same key now share their data automatically. There's also automatic cleanup when components unmount, and you can use reactive keys to refetch data when needed. Plus, we've given you more control over when cached data gets used.
Some of these features have already been made available in Nuxt v3 minor releases, because we've been rolling this out gradually. Nuxt v4 brings different defaults, and we expect to continue to work on this data layer in the days to come.
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.
With Nuxt 4, you will only need one tsconfig.json file in your project root!
This is probably the single issue that is most likely to cause surprises when upgrading, but it should also make your TypeScript experience much smoother in the long run. Please report any issues you encounter. 🙏
In parallel with the release of v4, we've been working on speeding up @nuxt/cli.
fs.watch APIs for fewer system resourcesThese improvements combined can make a really noticeable difference in your day-to-day development experience, and we have more planned.
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/kit. (This will particularly affect module authors.)Don't worry though — for most breaking changes, there are configuration options to revert to the old behavior while you adjust.
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.
We’ve also partnered with Codemod to automate many, though not all, migration steps:
npx codemod@latest nuxt/4/migration-recipe
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.
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.
This release is credit to so many people, particularly those who have been testing v4 compatibility mode over the past year. I'm really grateful — thank you for all your help!
Happy coding with Nuxt 4! 🚀
mlly (#28012)addServerImports (#32289)onWatcherCleanup to imports presets (#32396)<NuxtTime> prop types (#32547)render:html for server islands (#27889)compatibilityVersion: 4 (#27710)builder:watch hook (#27709)asyncData value behaviour (#27718)__NUXT__ after hydration (#27745)4 (7aae4033b)resolvePath utils as sync (655e1473d)tryResolveModule (2d136e04c)requireModule and tryRequireModule (#28013)useScriptCrisp scripts stub (0c3cc4cf3)#app/components/layout -> #app/components/nuxt-layout (209e81b60)dedupe option (#28151)installNuxtModule (501ccc375)oxc-walker (#32250)onPrehydrate transform (#32045)useAsyncData must return (#28259)deep default for useAsyncData & useFetch (#28564)deep option (bec85dfcd).nuxtignore examples for v4 structure (#32489)useNuxtData in data fetching composable pages (#32589)vite-plugin-checker separately (02d46dd3d)engines.node compatibility (a26322f5f)nuxi (9aa4c7c3b)nuxi version again (#30547)oxc-parser updates temporarily (1cd0fb5cb)nitro/templates directory (e531477f8)attw test for built packages (#30206)configResolved (8d3bd4f9f)render:html for server islands (#27889)compatibilityVersion: 4 (#27710)builder:watch hook (#27709)asyncData value behaviour (#27718)__NUXT__ after hydration (#27745)4 (7aae4033b)globalName property (#28391)compatibilityVersion: 3 (#32255)nuxt: ⚠️ Emit absolute paths in builder:watch hook (#27709)
nuxt: ⚠️ Improve default
asyncDatavalue behaviour (#27718)
nuxt: ⚠️ Remove
__NUXT__after hydration (#27745)
nuxt: ⚠️ Bump internal majorVersion to
4(7aae4033b)
nuxt: ⚠️ Remove unused
globalNameproperty (#28391)
kit,nuxt,schema: ⚠️ Remove other support for nuxt2/bridge (#28936)
kit: ⚠️ Do not check compatibility for nuxt version < 2.13 (f94cda4c8)
nuxt,schema: ⚠️ Remove support for
compatibilityVersion: 3(#32255)
nuxt: ⚠️ Don't rerun asyncdata w/ existing data in
useAsyncData(#32170)
nuxt: ⚠️ Bump
compatibilityDateto2025-07-15(e35e1ccb9)
kit,nuxt: ⚠️ Drop nuxt 2 + ejs template compile support (#27706)
nuxt: ⚠️ Move
#app/components/layout->#app/components/nuxt-layout(209e81b60)
kit,nuxt,vite,webpack: ⚠️ Remove legacy require utils (#28008)
globalName property (#28391)updateAppConfig in HMR (#28349)ssr: false (#28488)window access (d874726ff)resolveId from vite-node to resolve deps (#30922)isEqual from main ohash export (3ec1a1e5e)output.preserveModules (ce49734aa)#app-manifest import in dev mode (#31539)purgeCachedData until v4 (7aa3a01ae)purgeCachedData by default (06745604c).execute (d79e14612)compatibilityVersion: 3 (#32255)useAsyncData (#32170)errorValue/value to be undefined (7e4eac655)srcDir (#32487)@nuxt/cli (#32488)tsConfig doesn't exclude too many types (#32528)app/ and server/ folders into tsconfigs (#32592)typescript.hoist (#32601)tsconfig.server.json (#32594)compatibilityDate to 2025-07-15 (e35e1ccb9)scrollBehaviorType for hash scrolling (#32622)useAsyncData (#32170)compatibilityDate to 2025-07-15 (e35e1ccb9)#app/components/layout -> #app/components/nuxt-layout (209e81b60)