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.2

15 Jan 2025Where it was published

3.21.11 is the newest release of 3.x.

In short

1 new5 faster13 fixed17 internal

Security

19 advisories affect 3.15.2; 4.6.2 fixes the others

14 more

Release note

3.15.2 is the next regularly scheduled patch release.

Highlights

Startup performance improvements

It is worth noting that this release includes some pretty significant performance improvements which you should notice particularly in the startup time. In my tests in the nuxt monorepo,

fixturetime to vite build complete (v3.15.1)time to vite build complete (v3.15.2)
minimal850ms710ms
everything bagel3,021ms1,690ms

There's more improvement to do here but hopefully these are good numbers!

CLI refactor

To improve performance within Nuxt projects, we've published a new @nuxt/cli distribution of nuxi, which is used under-the-hood in nuxt (see issue). This should behave exactly the same and nothing needs to be updated in your projects (for example, you will continue to use the nuxi or nuxt commands). The only significant change is that it no longer inlines dependencies. Feedback is welcome 🙏

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

  • nuxt: Remove code duplication in client-only

  • nuxt: Use lighter @nuxt/cli dependency

  • kit: Remove iterations when resolving module path

  • nuxt: Avoid checking fs for existence of scanned pages

  • nuxt: Defer version/config warnings to after build

Fixes

  • nuxt: Collect all identifiers before extracting page metadata

  • nuxt: Don't hoist identifiers declared locally in definePageMeta when extracting page metadata

  • kit: Reorder #build to the end of tsConfig paths

  • nuxt: Use fullPath instead of empty string in router hmr

  • Relax nuxt version constraints to current

  • nuxt: Add import protection for @nuxt/cli

  • kit: Fully resolve plugin paths when normalising them

  • nuxt: Call page:loading:end only once with nested pages

  • nuxt: Warn about ignored char while parsing route segment

  • nuxt: Allow url-specific chars in vfs

  • nuxt: Do not warn about invalid characters in route groups/catchalls

  • vite: Provide fallback alias for #app-manifest

  • nuxt: Avoid invoking shouldPrefetch on the server side

  • nuxt: Decode id before resolving relative 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.