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

5 Jul 2023Where it was published

3.21.11 is the newest release of 3.x.

In short

1 new3 faster18 fixed16 internal

Security

17 advisories affect 3.6.2; 4.6.0 fixes the others

12 more

Release note

3.6.2 is the next patch release, with a raft of fixes including preparations for use without --shamefully-hoist and some fixes for data fetching within nested layouts/pages.

Upgrading

As usual, our recommendation for upgrading is to run:

nuxi 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: Don't run island transform plugin if disabled

  • nuxt: Allow hmr for server components in dev mode

  • nuxt: Use getters when constructing reactive routes

Fixes

  • nuxt: Only redirect if path is not the same as initial url

  • cli: Resolve @nuxt/ui-templates from modulesDir

  • nuxt, vite: Do not use cjs utils to resolve/alias vue

  • nuxt: Improve default prerender behaviour

  • vite: Greater type-safety within runtime vite-node

  • nuxt: Ensure static presets equivalent to nuxi generate

  • nuxt: Handle injecting multiple entry ids for styles

  • nuxt: Stop loading indicator on navigation failure

  • cli: Respect nitro ssl cert/key variables

  • nuxt: Include external layers in tsconfig.json scope

  • nuxt: Support custom route name meta with typedPages

  • vite: Remove @vue/ scoped libraries from resolutions

  • nuxt: Add layers in node_modules to tsconfig include

  • nuxt: Regenerate imports after template

  • vite: Fix issue detecting shadowed keyed composables

  • nuxt: Use $fetch.raw in dev client mode for islands

  • schema: Warn if user provides vite.publicDir

  • nuxt: Preserve old vnode when leaving nested route

  • kit: Ignore telemetry startup time (as it has prompt)

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.