Packages

nuxt

4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed

The latest release, 4.6.4, is affected by 4 advisories with no fixed version yet.See advisories
Your version

3.15.3

24 Jan 2025Where it was published

3.21.11 is the newest release of 3.x.

In short

1 breaking1 new7 faster9 fixed21 internal

Security

19 advisories affect 3.15.3; 4.6.2 fixes the others

14 more

Release note

3.15.3 is the next regularly scheduled patch release.

Highlights

CORS configuration for dev server

Alongside a range of improvements, we've also shipped a significant fix to impose CORS origin restrictions on the dev server. This applies to your Vite or Webpack/Rspack dev middleware only.

This is a significant/breaking change we would not normally ship in a patch but it is a security fix (see github.com/nuxt/nuxt/security/advisories/GHSA-4… and github.com/nuxt/nuxt/security/advisories/GHSA-2…) and we urge you to update ASAP.

You can configure the allowed origins and other CORS options via the devServer.cors options in your nuxt.config, which may be relevant if you are developing with a custom hostname:

export default defineNuxtConfig({
  devServer: {
    cors: {
      origin: ['https://custom-origin.com'],
    },
  },
})

Upgrading

As usual, our recommendation for upgrading is to run:

npx nuxi@latest upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

Changelog

compare changes

Performance

  • kit,nuxt: Don't resolve paths from local layers/modules

  • nuxt: Reduce number of mkdirSync calls

  • nuxt: Reduce unnecessary template updating

  • kit: Reduce duplication between findPath and resolvePath

  • kit: Run components compat check synchronously

  • nuxt: Early return from annotation for non-object syntax plugins

  • nuxt: Enable Transition component only on client side

Fixes

  • vite: Override previous #app-manifest alias

  • kit,nuxt,schema,vite: Improve watching behaviour

  • nuxt: Fall back to plugin.src for variable name generation

  • schema: Allow overriding dev/test environment value

  • vite: Drop unneeded call to invalidate module

  • vite: Add back invalidateModule call

  • nuxt: Do not warn about [[ optional dynamic params

  • vite: Inline shared folder in dev mode

  • nuxt: Deep clone extracted page meta

  • vite,webpack: Restrict access via cors to local origins + allow configuration via devServer.cors

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.