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

4 Nov 2024Where it was published

3.21.11 is the newest release of 3.x.

In short

14 new3 faster26 fixed3 changed41 internal

Security

19 advisories affect 3.14.0; 4.6.2 fixes the others

14 more

Release note

3.14.0 is the next minor release.

Highlights

Behind the scenes, a lot has been going on in preparation for the release of Nuxt v4 (particularly on the unjs side with preparations for Nitro v3!)

Faster starts powered by jiti

Loading the nuxt config file, as well as modules and other build-time code, is now powered by jiti v2. You can see more about the release in the jiti v2 release notes, but one of the most important pieces is native node esm import (where possible), which should mean a faster start. ✨

Shared folder for code and types shared with client/server

You should never import Vue app code in your nitro code (or the other way around). But this has meant a friction point when it comes to sharing types or utilities that don't rely on the nitro/vue contexts.

For this, we have a new shared/ folder (#28682). You can't import Vue or nitro code into files in this folder, but it produces auto-imports you can consume throughout the rest of your app.

If needed you can use the new #shared alias which points to this folder.

The shared folder is alongside your server/ folder. (If you're using compatibilityVersion: 4, this means it's not inside your app/ folder.)

rspack builder

We're excited to announce a new first-class Nuxt builder for rspack. It's still experimental but we've refactored the internal Nuxt virtual file system to use unplugin to make this possible.

Let us know if you like it - and feel free to raise any issues you experience with it.

👉 To try it out, you can use this starter - or just install @nuxt/rspack-builder and set builder: 'rspack' in your nuxt config file.

New composables

We have new useResponseHeader and useRuntimeHook composables (#27131 and #29741).

New module utilities

We now have a new addServerTemplate utility (#29320) for adding virtual files for access inside nitro runtime routes.

v4 changes

We've merged some changes which only take effect with compatibilityVersion: 4, but which you can opt-into earlier.

  1. Previously, if you had a component like ~/components/App/Header.vue this would be visible in your devtools as <Header>. From v4 we ensure this is <AppHeader>, but it's opt-in to avoid breaking any manual <KeepAlive> you might have implemented. (#28745).

  2. Nuxt scans page metadata from your files, before calling pages:extend. But this has led to some confusing behaviour, as pages added at this point do not end up having their page metadata respected. So we now do not scan metadata before calling pages:extend. Instead, we have a new pages:resolved hook, which is called after pages:extend, after all pages have been augmented with their metadata. I'd recommend opting into this by setting experimental.scanPageMeta to after-resolve, as it solves a number of bugs.

Roadmap to v3.15

They didn't quite make it in time for v3.14 but for the next minor release you can expect (among other things):

  • auto-imported directives from modules

  • 'isolated' page renders

  • Delayed hydration

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

Enhancements

  • deps: Upgrade to latest version of jiti

  • kit,nuxt,vite,webpack: Reimplement cjs utils using jiti

  • nuxt: Normalise component names to match nuxt pattern

  • kit,schema: Add addServerTemplate utility

  • nuxt: Add useResponseHeader composable

  • rspack,webpack: Add rspack builder

  • nuxt,schema: pages:resolved hook + scan meta post extend

  • nuxt: Allow enabling route props in definePageMeta

  • schema,nuxt: Add shared/ folder and #shared alias

  • nuxt: Allow chunk error or manifest update -> reload

  • nuxt: Add useRuntimeHook composable

Performance

  • nuxt: Remove unneeded second call to useNuxtApp

  • vite: Avoid redundant postcss plugins overwrite

  • kit,nuxt,vite,webpack: Hoist regex patterns

Fixes

  • nuxt: Simplify plugin InjectionType template conditional

  • nuxt: Access server build from webpack memfs

  • nuxt: Do not resolve non-absolute component paths

  • nuxt: Defer unsetting error handler until suspense resolves

  • nuxt: Pass DOMException as fetch abort exception

  • vite: Don't force protocol if disabled devServer.https

  • nuxt: Empty nitro buildDir in dev mode

  • nuxt: Don't resolve relative import type paths for deps

  • kit: Handle passing 'bare' relative paths to modules

  • kit: Try resolving module path from each node_modules dir

  • kit,vite,webpack: Resolve postcss paths from each modules dir

  • kit,vite,webpack: Strip node_modules/ from parent urls

  • nuxt: Add crossorigin attribute for stylesheets

  • nuxt: Use routeRules to hint pages to prerender

  • nuxt: Pass absolute external link urls to link:prefetch

  • nuxt: Error on build when required module is missing

  • nuxt: Prevent 404 when hitting component test endpoint

  • nuxt: Avoid throwing 404 error before middleware finishes

  • schema: Use ConfigLayer type from c12

  • nuxt: Fix nested page types in typedPages

  • nuxt: Allow islands to manipulate head client-side

  • vite: Dim repeat count in logs

  • schema: Mark configFile as required in layer type

  • nuxt: Remove vue compiler hints from auto import

  • vite: Update signature for createIsExternal

  • nuxt: Respect existing props value in definePageMeta

  • schema: Hoist nitropack/types to ensure api routes are typed

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.