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

9 Dec 2025Where it was published

3.21.11 is the newest release of 3.x.

In short

1 new13 fixed17 internal

Security

18 advisories affect 3.20.2; 4.6.2 fixes the others

13 more

Release note

3.20.2 is the next patch release.

Upgrading

Our recommendation for upgrading is to run:

npx nuxt upgrade --dedupe --channel=v3

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.

Note

This will only work if you already have a version of @nuxt/cli which has the --channel flag. If this does not work, you can instead run npx nuxi@latest for the initial upgrade.

Changelog

compare changes

Fixes

  • nitro: Do not show pretty error handler when testing

  • nuxt: Generate valid references for component declaration items

  • nuxt: Sync internal route before calling page:finish hook

  • nitro: Ensure html is a string before injecting error handler

  • nitro: Include layer server directories in tsconfig.server.json

  • nuxt: Ensure deduped async data executions return latest promise

  • kit,nuxt: Type + respect moduleDependencies by meta name

  • nuxt,schema: Ignore .d.vue.ts declarations

  • kit,nuxt: Protect against resolved nuxt module subpath

  • nuxt: Re-execute callOnce during HMR

  • nuxt: Resolve watch callback after reactive key change in useAsyncData

  • nuxt: Escape HTML in development error page stack trace

  • kit: Do not add resolved rootDir to cached layer config

  • kit,schema: Add moduleDependencies -> installModule

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.