Packages

@nuxt/rspack-builder

4.6.4 · 2 Nov 2026MIT590 / weekRepositoryHomepagenpmAtom feed

Your version

4.0.0

major15 Jul 2025Where it was published

4.6.4 is the newest release of 4.x.

In short

14 breaking1 new2 fixed4 changed45 internal

  • Breaking

    This is a stability-focused major release, introducing a few thoughtful breaking changes in order to improve development experience.

  • Breaking

    Although any major release brings breaking changes, one of our main aims for this release is to ensure that the upgrade path is as smooth as possible.

  • Breaking

    nuxt: ⚠️ 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 globalName property

  • Breaking

    kit,nuxt,schema: ⚠️ Remove other support for nuxt2/bridge

Security

Release note

The section about @nuxt/rspack-builder of a note shared by several packages.

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 useAsyncData and useFetch work better. Multiple components using the same key now share their data automatically. There's also automatic cleanup when components unmount, and you can use reactive keys to refetch data when needed. Plus, we've given you more control over when cached data gets used.

Some of these features have already been made available in Nuxt v3 minor releases, because we've been rolling this out gradually. Nuxt v4 brings different defaults, and we expect to continue to work on this data layer in the days to come.

Better TypeScript experience

Nuxt now creates separate TypeScript projects for your app code, server code, shared/ folder, and builder code. This should mean better autocompletion, more accurate type inference and fewer confusing errors when you're working in different contexts.

Tip

With Nuxt 4, you will only need one tsconfig.json file in your project root!

This is probably the single issue that is most likely to cause surprises when upgrading, but it should also make your TypeScript experience much smoother in the long run. Please report any issues you encounter. 🙏

Faster CLI and development

In parallel with the release of v4, we've been working on speeding up @nuxt/cli.

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

compare changes

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 hydration

  • kit: ⚠️ Drop support for building nuxt 2 projects

  • nuxt: ⚠️ Remove unused globalName property

  • kit,nuxt,schema: ⚠️ Remove other support for nuxt2/bridge

  • nuxt: Remove unneeded subpath import

  • nuxt,schema: ⚠️ Remove support for compatibilityVersion: 3

  • kit,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 globalName property

  • 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

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.