Skip to content

chore(deps): update nuxt core - #3265

Open
renovate[bot] wants to merge 4 commits into
mainfrom
renovate/nuxt
Open

chore(deps): update nuxt core#3265
renovate[bot] wants to merge 4 commits into
mainfrom
renovate/nuxt

Conversation

@renovate

@renovate renovate Bot commented Sep 18, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@nuxt/test-utils 4.1.0 → 4.3.4 age confidence
@nuxtjs/i18n>@nuxt/kit (source) 4.5.2 → 4.6.3 age confidence
nuxt (source) 4.5.2 → 4.6.3 age confidence
vue (source) 3.5.42 → 3.5.44 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

nuxt/test-utils (@​nuxt/test-utils)

v4.3.4

Compare Source

v4.3.4 is the next patch release.

👉 Changelog

compare changes

🩹 Fixes
  • runtime: test failure when module cached (#​1856)
  • runtime-utils: support registerEndpoint with FormData in jsdom (#​1846)
  • e2e: restore test context before running setup hooks (#​1855)
  • e2e: apply nuxtConfig overrides to dev server (#​1851)
  • config: prefer h3 version from nitro path (#​1844)
  • module: apply vitest setup only when loaded from vitest config (#​1834)
  • config: respect default resolve conditions in vitest browser mode (#​1843)
  • module: pass required token to open vitest ui in devtools (#​1841)
💅 Refactors
  • module: use package-manager-detector workspace + deno handling (1d59009c7)
🏡 Chore
  • cleanup example deps, unify vitest, and update knip config (#​1840)
❤️ Contributors

v4.3.3

Compare Source

v4.3.3 is the next patch release.

👉 Changelog

compare changes

🔥 Performance
  • use h3's toWebHandler instead of node-mock-http (abe8ad944)
  • resolve h3 from the project (b5d802f03)
  • replace estree-walker with oxc-walker (8e8ca5e8b)
  • replace local-pkg with exsolve (38938a879)
  • replace c12 with native dotenv parsing (26c72afa0)
  • inline destr and scule usage (e4bfd2ebe)
  • drop node-fetch-native polyfill (6b654de5c)
  • replace nypm with package-manager-detector (#​1828)
🩹 Fixes
  • runtime-utils: type registerEndpoint against the project h3 (#​1831)
  • e2e: restore console after use nuxt kit (#​1817)
  • config: exclude aliased mock packages from optimizeDeps in browser mode (#​1816)
  • runtime: setup nuxt once per worker in no-isolate (#​1821)
  • browser: correct render helper options type (#​1822)
🏡 Chore
  • move vue to peer dependencies (e70592ffa)
  • declare supported nuxt versions as peer dependency (b473892c9)
🤖 CI
❤️ Contributors

v4.3.2

Compare Source

v4.3.2 is the next patch release.

👉 Changelog

compare changes

🩹 Fixes
  • vitest-environment: keep vitest/environments import opaque to rolldown (6d1195d38)
❤️ Contributors

v4.3.1

Compare Source

v4.3.1 is the next patch release.

👉 Changelog

compare changes

🩹 Fixes
  • deps: allow vitest ^5 as peer dependency (#​1809)
🏡 Chore
🎉 New Contributors
❤️ Contributors

v4.3.0

Compare Source

v4.3.0 is the next minor release.

👉 Changelog

compare changes

🚀 Enhancements
  • runtime-utils: add unmockNuxtImport helper (#​1795)
  • config: support vitest 5 (#​1802)
🩹 Fixes
  • config: default nuxt test pattern to nested for simple non-nuxt setup (#​1801)
✅ Tests
  • make sure tests are collected at runtime, not statically (#​1797)
🎉 New Contributors
❤️ Contributors

v4.2.0

Compare Source

v4.2.0 is the next minor release.

👉 Changelog

compare changes

🚀 Enhancements
  • browser: add render helper for vitest browser mode (#​1725)
  • runtime-utils: add spy option to mount + render helpers (#​1762)
🩹 Fixes
  • runtime-utils: mockNuxtImport sourcemap mapped position (#​1787)
  • config: tolerate non-cloneable values when cloning config (#​1771)
  • e2e: honour setupTimeout in playwright + surface server logs (#​1785)
  • e2e: add explanation if server exited before being ready (#​1761)
  • module: handle string presets in auto-imports (#​1784)
  • config: don't run includeSource in both projects in defineVitestConfig (#​1763)
  • e2e: use taskkill to kill processes on windows (#​1760)
  • config: support nuxt v5 with nitro vite environment (#​1758)
🏡 Chore
  • avoid missing file extension warning in test/examples (#​1775)
  • exempt first-party packages from pnpm minimumReleaseAge (#​1774)
  • replace latest ranges with caret ranges (#​1773)
  • move vite environment api tests to example tests (#​1755)
✅ Tests
  • re-enable bun browser e2e on windows (#​1791)
🤖 CI
  • migrate to uppt for release workflow (#​1792)
🎉 New Contributors
❤️ Contributors
nuxt/nuxt (@​nuxtjs/i18n>@​nuxt/kit)

v4.6.3

Compare Source

v4.6.3 is the next patch release.

👉 Changelog

compare changes

🚨 Security fixes
🔥 Performance
  • vite: skip compiling plain style blocks in the server build (#​36711)
  • nitro,nuxt,rspack,webpack: bundle esm vue + reuse caches (#​36710)
  • vite: avoid quadratic nested dir check for fs.allow (#​36702)
  • nuxt: server render internal custom links without RouterLink (#​36707)
  • nuxt: skip unneeded typed routes generation (#​36645)
🩹 Fixes
  • nitro: don't share prerender hints with self-fetched requests (#​36705)
  • nuxt: defer app scope cleanup on external navigation (#​36713)
  • nuxt: prevent useCookie CookieStore sync from rewriting with refresh (#​36673)
  • nuxt: only return redirects from navigateTo while middleware runs (#​36650)
  • nuxt: remove purged entries from _asyncData (#​36709)
  • vite: skip quoted import.meta keys + limit replace to client dev (#​36703)
  • nuxt: hide RouteLocationRaw from navigateTo's public return type (#​36691)
  • nuxt: tree-shake auto-imported #app composables (#​36696)
  • nuxt: don't treat constrained route rules as covering dynamic pages (#​36701)
  • nuxt: include shared/ in build cache hash (#​36704)
  • nuxt: hash keyed function ids + page import names relative to rootDir (#​36697)
  • nuxt: encode page paths before matching route rule keys (#​36683)
  • nuxt: handle rejected updateCallbackDone of aborted view transition (#​36639)
  • ui-templates: keep loading shader proportions on narrow screens (#​36654)
  • nuxt: reject case-dependent route rule constraints w/ sensitive: false (#​36708)
  • nuxt: don't case-fold regex constraints in route rule keys (#​36694)
  • nuxt: normalise page prefix when finding route rule exceptions (#​36685)
  • vite: mirror ssr invalidations for created and deleted files (634cba64c)
  • nitro: keep noScripts wildcard patterns single-segment (fa323db7d)
  • deps: update unrouting to v0.3.1 (#​36663)
  • nuxt: avoid self-referencing nuxt/schema augmentation (#​36633)
  • nuxt: let nightly runtime resolve its own nuxt/* imports (#​36632)
  • nuxt: don't warn for vite+ vite.config files (#​36628)
  • kit: keep generated declaration first in tsconfig include (#​36627)
  • nuxt: clamp numeric v-for sources in island renders at render time (#​36623)
  • rspack,webpack: register vue-loader plugin only once per config (#​36622)
  • nitro: abort the portable request when the client disconnects (#​36652)
  • deps: update nitropack to 2.13.5 + drop obsolete workarounds (#​36649)
📖 Documentation
  • note provide/inject limit in server components (#​35837)
  • use American spelling in a few guides (#​36706)
  • document controlling prefetch hints via build:manifest hook (#​36695)
  • update StackBlitz link to point to version 4 (#​36674)
  • link to the 2.x docs (#​36640)
  • clarify that island props must be validated before iteration (4b12d15c9)
✅ Tests
  • list NUXT_B4023 as main-only (4fd54ff9a)
  • wait for leave transition before each scroll behaviour test (453406999)
  • vite: assert spa server bundle does not ship the app (#​36699)
  • nuxt: cover route rule coverage under a base url (#​36682)
  • list NUXT_B9006 as main-only (e107e0f40)
🤖 CI
  • only run full checks for the last merge queue entry (132698a46)
  • run a reduced matrix in the merge queue (7d228ba4b)
  • compare merge queue changes against the base branch (bad8c3637)
  • notify resolved issues after publishing a release (9d47884f3)
  • remove broken ai-moderator and ecosystem-ci trigger workflows (1d89ad434)
🎉 New Contributors
❤️ Contributors

v4.6.2

Compare Source

v4.6.2 is the next patch release.

👉 Changelog

compare changes

🩹 Fixes
  • nitro: apply useHeadSafe rules to server island head (493565e99)
  • nitro-server: read router params from the path h3 matched (010f6b43d)
  • nitro: match server route rules case-insensitively unless routing is sensitive (f6cfee52c)
  • nuxt: resolve rooted paths through the URL parser (#​36617)
  • nuxt: resolve empty route types in shared context (#​36576)
  • nitro: preserve server tsconfig with relocated build dir (#​36494)
  • nuxt: fix scroll offset for IDs starting with numbers (#​36524)
  • kit: do not exclude module directories with a dot in their name from app tsconfig (#​36331)
  • nuxt: detect vapor slots with rawVaporSlotKey from vue (#​36614)
  • nuxt: keep middleware layout when restoring deferred prerendered route (#​36560)
  • schema: provide default value for experimental.typescriptPlugin (#​36561)
  • vite: only replay compile error overlays to newly loaded pages (#​36611)
  • nuxt: re-export AnyFetchPath for emitted server route types (#​36610)
  • vite: warm up the dev ssr entry from a nitro plugin (#​36615)
  • nitro: avoid unused h3 imports in nuxt/server runtime (#​36609)
  • vite-server: scope asset url helpers to the build (#​36591)
  • nuxt: resolve nuxt/app to the app's runtime (#​36587)
  • kit: lowercase filename-derived handler method on nitro v2 (#​36567)
  • nuxt,nitro: normalise string/array appMiddleware (#​36565)
  • nitro: pass response headers to render:response listeners (#​36583)
  • vite: resolve inlined vue to its bundler build in dev (#​36569)
  • nuxt: don't start a page transition with no page to leave (#​36535)
  • nuxt: preserve error state on aborted or cancelled navigation (#​36546)
  • vite,nitro: link null-byte virtual css through /@id/ in dev (#​36549)
  • kit: resolve module dependencies from the declaring module (#​36542)
  • nitro: only disable h3 + nitro presets when nitroAutoImports is off (#​36548)
  • nitro,vite: don't access unspecified dependencies (#​36541)
  • nitro: don't inline deps under absolute transpile dirs (#​36540)
  • vite-server: respect spa loading template location (#​36536)
💅 Refactors
  • webpack,rspack: inline friendly errors plugin (#​36568)
📖 Documentation
  • remove DeepWiki badge (#​36616)
  • rename H(TTP) to HTTP (#​36559)
  • mention proxy route rule (4a529be68)
  • reference definePlugin and defineNitroPlugin in server plugin tip (64b8e0334)
  • open a PR to list a module (e551df267)
  • clarify testing environments, runners, and config (#​32963)
  • align spa loading template references (#​36552)
  • explain how to disable iOS Safari phone number detection (#​36539)
  • fix outdated internal links (#​36550)
  • explain how to restore nitro auto-imports with compat v5 (7499a445b)
  • add spa-loading-template documentation (#​36537)
🏡 Chore
✅ Tests
  • wait for scroll to settle in route-scroll e2e (ca784deb7)
🤖 CI
  • comment nuxt.com preview links on docs pull requests (#​36594)
  • regenerate kit inlinedDependencies in autofix (4b6da3a29)
  • remove docs deploy triggers (917bdf218)
🎉 New Contributors
❤️ Contributors

v4.6.1

Compare Source

v4.6.1 is the next patch release.

👉 Changelog

compare changes

🔥 Performance
  • nitro: build the portable event's web view on first access (cffb182d6)
🩹 Fixes
  • vite: match vite 8.1+ optimizer messages for deps hint (#​36525)
  • nuxt: accept any baseURL when fetch response type is named (#​36523)
  • nitro: resolve nitropack/types declarations under nodenext (242e1971e)
  • nuxt: allow false in setPageLayout types (#​36506)
  • nuxt: align Serialize object types with JSON (#​36503)
  • vite: don't abort dep scan on virtual imports in installed packages (#​36477)
  • nuxt: update publishConfig config export extension (64fa191cb)
  • kit: install the package a missing subpath belongs to (#​36507)
  • vite-server: use the configured outDir as the public directory for non-ssr environment (#​36501)
  • kit,nitro: match dev handler paths on both nitro majors (#​36515)
  • nuxt: preserve onServerPrefetch for useId hydration (#​36430)
  • vite-server: include the request in dev error reports (#​36489)
  • nitro: register each dev server handler once (#​36493)
  • nitro: pass RequestEvent to nuxt dev server handlers (e6beceea2)
  • nuxt: type the global $fetch with nuxt's TypedFetch (#​36492)
  • vite-server: work with deploy target plugins in dev (#​36491)
  • schema: ignore .wrangler directory (#​36487)
  • vite-server: pass the path to the error page render (#​36488)
  • nuxt,vite: disable dev error broadcast if BroadcastChannel throws (#​36480)
  • kit: align semantic version regexp with nightly version format (#​36479)
  • nuxt: export types reachable from async data composables (#​36478)
  • vite: detect enclosing string delimiter in inline style urls (#​36476)
  • schema: type the nuxt dev server handler variant (452052793)
  • nitro: inline nuxt runtime when resolved to windows paths (21657c6fc)
  • nitro: resolve unhead from nuxt in server bundle (dc1e2d6e6)
💅 Refactors
  • kit: use package-manager-detector workspace + deno handling (1563a6d25)
📖 Documentation
  • document dev server handlers and nuxt/server scope (7c36a1352)
  • fix nightly examples (#​36486)
🏡 Chore
✅ Tests
  • resolve temporary fixture paths on macos (30742865c)
  • update test expectation (1f22a114d)
🤖 CI
🎉 New Contributors
❤️ Contributors

v4.6.0

Compare Source

v4.6.0 is the next minor release.

📣 Some news

🖥️ Nuxt CLI v4

Alongside the release of Nuxt v4.6, today also brings a new major release of the Nuxt CLI: @nuxt/cli v4. It ships as a dependency of nuxt, so you'll get it automatically when you upgrade.

Most of what's new is in nuxt dev:

  • an interactive terminal UI, showing URLs, startup progress and keyboard shortcuts, with panels to dive into error logs, routes, network requests and more
  • the dev server gives you more info, such as why it reloaded or restarted, which nuxt.config keys changed, where the time went during a slow start or build, and how long each module took to set up
  • a CLI-level error channel rendered with my-bad (see below), powering things like automatically reloading when a syntax error in nuxt.config.ts is fixed
  • a lock file in .nuxt/, which lets a second nuxt dev (say, one started by an agent) take over or defer to the one you started, and powers new nuxt curl and nuxt task commands that talk to the running server

There's also a new nuxt docs "<query>" search, and nuxt preview --takeover can replace a running preview server. And in general nuxt/cli is a lot smaller and starts a lot faster:

v3.37 v4.0
@nuxt/cli install size 13.1 MB 3.5 MB -73%
@nuxt/cli dependencies 70 31 -56%
nuxt dev: first paint 330 ms 50 ms 6.6x faster
nuxt dev: port bound 338 ms 104 ms 3.2x faster
nuxt dev: memory at rest (Linux) 630 MB 440 MB -30%
nuxt-dev

Although this is a major version, none of the changes should be breaking for Nuxt v4 users: we require Node.js v22.21+, v24.11+ or v26+, we drop nuxt init and only support npm create nuxt@latest, and Nuxt 2 and @nuxt/bridge are no longer supported.

👉 Check out the full Nuxt CLI v4 release notes for everything that's changed.

💡 A server-agnostic Nuxt

The biggest thing about this release is our move towards making Nuxt server-agnostic.

I feel that freedom of choice is very much a fundamental value of the web, and one that unites the whole Nuxt team.

You can use pages/ (with vue-router) or not. You can use Vite, webpack or Rspack to bundle your code. You can pick from dozens of providers to deploy to, pick any image or font provider, choose any database adapter. In every case, the framework is the same.

The server side was different. #app composables imported h3 types, server code imported from h3 and nitropack, and every module that touched the server was tied to whichever major version of those packages Nuxt happened to depend on.

This has become particularly clear as we have been upgrading to new majors of h3 and nitro, which ship breaking changes with a cascading effect throughout the whole ecosystem.

👉 This release changes that.

Alongside explicitly defining our public API in nuxt/kit (which now does not refer to external packages), Nuxt now specifies our own types for the request event, route rules and typed $fetch, and we expose an import surface (nuxt/server) for the server utilities that will be needed by most apps.

This is the culmination of work we started almost a year ago, making it possible to use any server builder with Nuxt, not just Nitro (#​33462).

Of course, under the hood, nuxt/server is still powered by Nitro by default - though we are also announcing a second, experimental implementation, @nuxt/vite-server, which allows pure-Vite server builds using the Vite Environment API.

[!IMPORTANT]
We believe that Nitro is still the right choice for almost everyone.

🌟 We see a number of key benefits for nuxt/server.

  1. it smooths the upgrade to Nuxt 5, which moves to Nitro v3 and h3 v2. Server code written against nuxt/server on 4.6 runs unchanged there, so a module can ship one file for both.
  2. it decouples Nuxt from the Nitro release cycle. Because we 'own' the API, we can adapt to breaking changes in Nitro or h3 without requiring a future major - and we can release Nuxt majors without having to wait for upstream releases.
  3. it makes Nuxt's code more maintainable. It helps us preserve the separation of concerns between our API - /app and /server - and the bundler + server that you ultimately want to build your app.

... and there are a number of other benefits too, from a single type surface to being able to iterate more quickly on features.

Finally, I want to say a special thank-you to @​pi0, whose relentless focus on server agnosticism and work on h3, Nitro and web-standard server primitives over the last few years is what makes a portable RequestEvent possible at all. Thank you, Pooya. ❤️

Almost every feature in this release is already in the Nuxt 5 branch, and most of the remaining Nuxt 5 defaults can be tested today with future.compatibilityVersion: 5 (more details below!).

[!TIP]
Nuxt 3 reached end-of-life on July 31, 2026, so there is no 3.x release alongside this one. If you're still on v3, the upgrade guide is waiting for you.

👀 Highlights

🤷 If you've read this far I'm afraid I have bad news for you: there's a lot more still to say! Nuxt 4.6 is one of our biggest minor releases, with over 420 commits since v4.5.2.

... so, you might want to grab a coffee! ☕️

🧩 nuxt/server

It has been asked for for a long time, and it now exists (#​36275)!

nuxt/server is a new import source for server code: handlers, middleware and utilities - a complement to nuxt/app. Where nuxt/app is for the part of your application that also runs in the browser, nuxt/server is for the part that only runs on the server.

import { defineEventHandler, getQuery } from 'nuxt/server'

export default defineEventHandler((event) => {
  const { name } = getQuery<{ name?: string }>(event)
  return { message: `Hello, ${name ?? 'world'}!` }
})

The utilities use web standards and are typed against a portable RequestEvent:

event.req         // Request
event.url         // URL
event.res         // { status, statusText, headers }
event.res.headers // Headers
event.context     // per-request context

Under @nuxt/nitro-server they are backed by Nitro and h3, but you never import from either.

So the same handler runs under Nitro v2, Nitro v3 or @nuxt/vite-server, and a module that imports from nuxt/server doesn't need a peer dependency on h3 or nitropack.

We think this will make a big difference in smoothing out the upgrade to Nuxt v5 and Nitro v3.

There is a typing benefit too. We no longer hoist h3 or Nitro types into your app to type useRequestEvent, $fetch or route rules, which removes a source of type conflicts when versions differ (#​36212, #​36214, #​36293).

The surface is small, and covers what published modules and user code typically need: defineEventHandler, createError/isNuxtError, request URL, headers, query, body (plain and validated with any Standard Schema library or a function), cookies, redirects, response status, getRouterParam(s), getRequestIP, handleCors, getRouteRules, useRuntimeConfig, useAppConfig and sessions.

import { defineEventHandler, readValidatedBody } from 'nuxt/server'
import { z } from 'zod'

export default defineEventHandler(async (event) => {
  const user = await readValidatedBody(event, z.object({ name: z.string() }))
  return { created: user.name }
})

We encourage you to use web APIs (event.req.headers, for example), or raise an issue if there's functionality you're missing from nuxt/server 🙏

If you do need to step outside nuxt/server for a particular handler, don't worry! Nothing has been taken away: import defineEventHandler and the helpers you need from h3 or nitropack/runtime as before, and that handler works exactly as it did on Nuxt 4.5.

import { defineEventHandler, readMultipartFormData } from 'h3'

export default defineEventHandler(async (event) => {
  const parts = await readMultipartFormData(event)
  return { received: parts?.length ?? 0 }
})

[!IMPORTANT]
On Nuxt 4, the auto-imported defineEventHandler, getQuery, readBody and the rest are still h3's own helpers, which take a different shape of event. Import from nuxt/server explicitly, including defineEventHandler to use the new server runtime. If you mix the two, you'll see a NUXT_E8012 error which should tell you which import to change.

A few helpers also behave differently from their h3 v1 namesakes: sendRedirect returns the response rather than sending it, createError takes status and statusText, and response headers are set through event.res.headers. The upgrade guide has a table of the differences.

Nothing in this release requires a migration. But if you have server code you'd like to make portable ahead of Nuxt 5, this is the best way.

👉 Read the server imports guide.

🔐 appSecret and sessions

Nuxt now has a root application secret: runtimeConfig.appSecret, set with NUXT_APP_SECRET (#​35874, thanks to @​onmax). Modules and server features derive purpose-specific secrets from it with deriveSecret(purpose), so NUXT_APP_SECRET is the only secret you need to configure.

openssl rand -base64 32

In development Nuxt generates and persists one if none is configured (and warns the first time a derived secret is used). Builds never generate one.

The first thing to use it is a set of session helpers in nuxt/server (#​36358). Sessions are sealed into a cookie with iron, so there's no server-side storage to configure:

import { defineEventHandler, useSession } from 'nuxt/server'

export default defineEventHandler(async (event) => {
  const session = await useSession<{ visits: number }>(event)
  await session.update(data => ({ visits: (data.visits ?? 0) + 1 }))
  return { visits: session.data.visits }
})

[!NOTE]
As a reminder, runtime config keys prefixed with app (runtimeConfig.app, runtimeConfig.appSecret) are reserved for Nuxt.

🎯 Typed $fetch, rebuilt

$fetch and useFetch have been typed from your server routes for a long time. But the types were derived from Nitro's InternalApi interface, and past a few hundred routes they hit TypeScript's instantiation limit with the familiar TS2589: Type instantiation is excessively deep and possibly infinite.

We've rebuilt typed fetch on top of fetchdts (#​36238). Nuxt compiles your server routes into a route tree with an exact-match table for static paths and accessors specialised to your route set. Resolution cost now scales with call sites, not with route count:

routes before after
100 1,397,361 instantiations / 0.77s 51,558 / 0.26s
300 5,774,425 / 3.49s (TS2589) 51,558 / 0.16s
1000 12,831,467 / 7.44s (TS2589) 51,558 / 0.20s
3000 (200 call sites) 71,875,148 / 53.63s (TS2589) 101,678 / 0.62s

Peak memory for the same runs dropped from 946 MB to 140 MB. 🔥

Plus, the route set also carries the body, query and headers a handler validates, so calls are checked more tightly than before:

// server/api/users.post.ts validates { title: string, count: number }
await $fetch('/api/users', { method: 'post', body: { title: 'a', count: 1 } })
await $fetch('/api/users', { method: 'post', body: { title: 'a', count: 'no' } })
//                                                                ^ not assignable to number
await $fetch('/api/users', { method: 'post' })
//           ^ body is required

On Nuxt 4 this is opt-in, because there are small changes to type inference, and hand-written ServerRoutes augmentations need a small rewrite. It is the default in Nuxt 5.

export default defineNuxtConfig({
  experimental: {
    routeTypedFetch: true,
  },
})

There's also a new experimental.strictRouteTypes option to reject calls to paths that don't exist (otherwise these just return unknown), and an 'isomorphic' mode that types your pages as GET routes too if you want to be able to $fetch from the Vue renderer with type safety.

👉 Read more in the experimental features docs.

🐛 Better errors in development with my-bad

Server-side errors in development used to look like this:

ReferenceError: foo is not defined
    at Object.<anonymous> (/_nuxt/app/pages/index.vue:1:1)

There was no source position or code frame, and the Youch iframe we rendered could not show you the frame in your own source either. Both are now fixed (#​36258, nuxt/cli#1518).

Dev SSR stack traces are now mapped before anything reads the error, and the Youch overlay has been replaced with my-bad. It renders into your app's own error page as an overlay (or as a standalone page when the app can't render one), with the mapped stack trace and a code frame from your source, and the same report is printed in your terminal. We are still working with @​atinux, @​HugoRCD and @​antfu to make these pages nicer still.

my-bad-ssr-expanded-dark my-bad-ssr-copymenu-dark

With Nuxt CLI v4, there is a single live error channel at the CLI level. It survives worker restarts, so (for example) a syntax error in nuxt.config.ts will live-reload the page once you fix it. Each error is rendered once rather than at every layer it passes through, and the same channel streams build progress and app logs to the dev panel.

🎨 A new loading screen, 404 and error pages

@​HugoRCD has redrawn the loading screen you see while the dev server starts. It is now a WebGL2 particle field that traces a mountain range behind the Nuxt lockup (#​36178), using a single shader and a single draw call. Without WebGL2 it falls back to the static lockup, and with prefers-reduced-motion the animation stops. Try hovering over it. 🏔️

Hugo also gave the built-in 404 and error pages a neutral palette and lighter type (#​36255), and @​MirkoJa added a back button to the 404 page (#​35688).

404-page-dark
⚡️ Vue Vapor support

Nuxt now supports Vue 3.6's Vapor Mode in interop mode (#​35759). Your app root stays on the virtual DOM, and you can opt individual components or pages into Vapor by adding the vapor attribute to <script setup>:

export default defineNuxtConfig({
  vue: {
    vapor: true,
  },
})
<script setup vapor lang="ts">
const count = ref(0)
</script>

<template>
  <button @click="count++">
    count is {{ count }}
  </button>
</template>

Routing, useAsyncData, layouts and most built-in components keep working unchanged. Along the way we made the auto-import loader, useAsyncData, definePageMeta and slot inspection Vapor-aware, and we now have a Vapor test suite so we can track what's supported.

[!NOTE]
This requires Vue ^3.6.0-rc.2 or newer. See the known limitations and try it in a fresh project first.

🧩 Addons for useFetch and useAsyncData

@​cernymatej has added an addons option to the createUseFetch and createUseAsyncData factories (#​35797). An addon can declare custom call-site options, adjust the merged options, wrap the handler with middleware, and extend what the composable returns, and it can be reused across as many custom instances as you like.

const refreshOnFocus = defineUseFetchAddon({
  setup: (options: UseFetchAddonOptions<{ refreshOnFocus?: boolean }>) => {
    if (import.meta.server || !options.refreshOnFocus) { return }

    return (asyncData) => {
      const focused = useWindowFocus()
      watch(focused, focused => focused && asyncData.refresh())
      return { focused }
    }
  },
})

export const useApiFetch = createUseFetch({ baseURL: '/api', addons: [refreshOnFocus] })
<script setup lang="ts">
const { data, focused } = await useApiFetch('/todos', { refreshOnFocus: true })
</script>

This resolves a long list of feature requests for useAsyncData and useFetch (refresh on focus, polling, retries, auth headers and more) without making the core composables opinionated about any of them.

👉 Read about defineUseFetchAddon and defineUseAsyncDataAddon.

🚀 Performance

There is a lot of performance work in this release.

  • <NuxtLink> renders 58% faster on the server (#​36015). Internal links are now rendered as a plain <a> with no useLink, no computed and no reactive state. Rendering 200 links went from 1.36ms to 0.57ms, which is 1.4x faster than a bare <RouterLink>.
  • Early 404s (#​36117). With experimental.early404, page routes are compiled into a static matcher at build time and requests that can't match any page skip creating the Vue app, running plugins and middleware entirely. On an app with 30 pages and ~23ms of boot work per render, a JSON 404 went from 37.1ms to 0.3ms.
  • **Templates decla

[!IMPORTANT]
✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Sep 18, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Scope: all 3 workspace projects
✓ Lockfile passes supply-chain policies (verified 1m ago)
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 49, reused 0, downloaded 0, added 0
Progress: resolved 100, reused 0, downloaded 0, added 0
Progress: resolved 109, reused 0, downloaded 0, added 0
Progress: resolved 113, reused 0, downloaded 0, added 0
Progress: resolved 125, reused 0, downloaded 0, added 0
Progress: resolved 214, reused 0, downloaded 0, added 0
Progress: resolved 290, reused 0, downloaded 0, added 0
Progress: resolved 357, reused 0, downloaded 0, added 0
Progress: resolved 435, reused 0, downloaded 0, added 0
Progress: resolved 482, reused 0, downloaded 0, added 0
Progress: resolved 572, reused 0, downloaded 0, added 0
Progress: resolved 576, reused 0, downloaded 0, added 0
Progress: resolved 578, reused 0, downloaded 0, added 0
Progress: resolved 582, reused 0, downloaded 0, added 0
Progress: resolved 717, reused 0, downloaded 0, added 0
Progress: resolved 782, reused 0, downloaded 0, added 0
Progress: resolved 899, reused 0, downloaded 0, added 0
Progress: resolved 1030, reused 0, downloaded 0, added 0
Progress: resolved 1109, reused 0, downloaded 0, added 0
Progress: resolved 1126, reused 0, downloaded 0, added 0
Progress: resolved 1127, reused 0, downloaded 0, added 0
Progress: resolved 1129, reused 0, downloaded 0, added 0
Progress: resolved 1141, reused 0, downloaded 0, added 0
Progress: resolved 1324, reused 0, downloaded 0, added 0
Progress: resolved 1367, reused 0, downloaded 0, added 0
Progress: resolved 1419, reused 0, downloaded 0, added 0
Progress: resolved 1425, reused 0, downloaded 0, added 0
Progress: resolved 1432, reused 0, downloaded 0, added 0
Progress: resolved 1434, reused 0, downloaded 0, added 0
Progress: resolved 1549, reused 0, downloaded 0, added 0
Progress: resolved 1628, reused 0, downloaded 0, added 0
Progress: resolved 1785, reused 0, downloaded 0, added 0
Progress: resolved 1959, reused 0, downloaded 0, added 0
Progress: resolved 1961, reused 0, downloaded 0, added 0
Progress: resolved 2111, reused 0, downloaded 0, added 0
Progress: resolved 2268, reused 0, downloaded 0, added 0
Progress: resolved 2295, reused 0, downloaded 0, added 0
Progress: resolved 2296, reused 0, downloaded 0, added 0
Progress: resolved 2297, reused 0, downloaded 0, added 0
[WARN] 7 deprecated subdependencies found: @types/[email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Progress: resolved 2297, reused 0, downloaded 0, added 0, done
[ERR_PNPM_PEER_DEP_ISSUES] Unmet peer dependencies

✕ unmet peer nuxt
  Installed: 4.6.3
  Wanted:
    4.5.2:
      @nuxt/[email protected]
hint: To disable failing on peer dependency issues, add the following to pnpm-workspace.yaml in your project root:

  strictPeerDependencies: false

@vercel

vercel Bot commented Sep 18, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
docs.npmx.dev Ready Ready Preview Nov 1, 2026 1:51am UTC
npmx.dev Error Error Nov 1, 2026 1:51am UTC
1 Skipped Deployment
Project Deployment Actions Updated
npmx-lunaria Ignored Ignored Nov 1, 2026 1:51am UTC

Request Review

@codecov

codecov Bot commented Sep 18, 2026 •
edited
Loading

Copy link
Copy Markdown

❌ 5 Tests Failed:

Tests completed Failed Passed Skipped
2807 5 2802 6
View the top 3 failed test(s) by shortest run time 
test/nuxt/a11y.spec.ts > test/nuxt/a11y.spec.ts
Stack Traces | 0s run time 
Error: Failed to import test file .../runner/work/npmx.dev/npmx..../test/nuxt/a11y.spec.ts
 ❯ node_modules/.cache.../676879ce89bf73d10ed3edb978c6e79ac1de83ce/deps/plugins.DPQHVT0p-BlQrJL1P.js?v=cdf415d4:5847:5
 ❯ collectTests node_modules/.cache.../676879ce89bf73d10ed3edb978c6e79ac1de83ce/deps/plugins.DPQHVT0p-BlQrJL1P.js?v=cdf415d4:5823:3
 ❯ startTests node_modules/.cache.../676879ce89bf73d10ed3edb978c6e79ac1de83ce/deps/plugins.DPQHVT0p-BlQrJL1P.js?v=cdf415d4:6511:17

Caused by: Caused by: SyntaxError: Identifier 'vi' has already been declared
test/nuxt/components/HeaderConnectorModal.spec.ts > test/nuxt/components/HeaderConnectorModal.spec.ts
Stack Traces | 0s run time 
Error: Failed to import test file .../runner/work/npmx.dev/npmx..../nuxt/components/HeaderConnectorModal.spec.ts
 ❯ node_modules/.cache.../676879ce89bf73d10ed3edb978c6e79ac1de83ce/deps/plugins.DPQHVT0p-BlQrJL1P.js?v=cdf415d4:5847:5
 ❯ collectTests node_modules/.cache.../676879ce89bf73d10ed3edb978c6e79ac1de83ce/deps/plugins.DPQHVT0p-BlQrJL1P.js?v=cdf415d4:5823:3
 ❯ startTests node_modules/.cache.../676879ce89bf73d10ed3edb978c6e79ac1de83ce/deps/plugins.DPQHVT0p-BlQrJL1P.js?v=cdf415d4:6511:17

Caused by: Caused by: SyntaxError: Identifier 'vi' has already been declared
test/nuxt/components/LicenseDisplay.spec.ts > test/nuxt/components/LicenseDisplay.spec.ts
Stack Traces | 0s run time 
Error: Failed to import test file .../runner/work/npmx.dev/npmx..../nuxt/components/LicenseDisplay.spec.ts
 ❯ node_modules/.cache.../676879ce89bf73d10ed3edb978c6e79ac1de83ce/deps/plugins.DPQHVT0p-BlQrJL1P.js?v=cdf415d4:5847:5
 ❯ collectTests node_modules/.cache.../676879ce89bf73d10ed3edb978c6e79ac1de83ce/deps/plugins.DPQHVT0p-BlQrJL1P.js?v=cdf415d4:5823:3
 ❯ startTests node_modules/.cache.../676879ce89bf73d10ed3edb978c6e79ac1de83ce/deps/plugins.DPQHVT0p-BlQrJL1P.js?v=cdf415d4:6511:17

Caused by: Caused by: TypeError: Cannot read properties of undefined (reading 'config')
 ❯ initSuite node_modules/.cache.../676879ce89bf73d10ed3edb978c6e79ac1de83ce/deps/plugins.DPQHVT0p-BlQrJL1P.js?v=a8139543:5181:23
 ❯ createSuiteCollector node_modules/.cache.../676879ce89bf73d10ed3edb978c6e79ac1de83ce/deps/plugins.DPQHVT0p-BlQrJL1P.js?v=a8139543:5076:2
 ❯ Object.suiteFn node_modules/.cache.../676879ce89bf73d10ed3edb978c6e79ac1de83ce/deps/plugins.DPQHVT0p-BlQrJL1P.js?v=a8139543:5259:10
 ❯ chain node_modules/.cache.../676879ce89bf73d10ed3edb978c6e79ac1de83ce/deps/plugins.DPQHVT0p-BlQrJL1P.js?v=a8139543:4336:14
 ❯ .../nuxt/components/LicenseDisplay.spec.ts:4:1
test/nuxt/composables/use-command-palette-commands.spec.ts > test/nuxt/composables/use-command-palette-commands.spec.ts
Stack Traces | 0s run time 
Error: Failed to import test file .../runner/work/npmx.dev/npmx..../nuxt/composables/use-command-palette-commands.spec.ts
 ❯ node_modules/.cache.../676879ce89bf73d10ed3edb978c6e79ac1de83ce/deps/plugins.DPQHVT0p-BlQrJL1P.js?v=cdf415d4:5847:5
 ❯ collectTests node_modules/.cache.../676879ce89bf73d10ed3edb978c6e79ac1de83ce/deps/plugins.DPQHVT0p-BlQrJL1P.js?v=cdf415d4:5823:3
 ❯ startTests node_modules/.cache.../676879ce89bf73d10ed3edb978c6e79ac1de83ce/deps/plugins.DPQHVT0p-BlQrJL1P.js?v=cdf415d4:6511:17

Caused by: Caused by: SyntaxError: Identifier 'vi' has already been declared
vitest unhandled errors > Unhandled Error: Failed to run the test /home/runner/work/npmx.dev/npmx.dev/test/nuxt/components/Input/Base.spec.ts.
Stack Traces | 0s run time 
Error: Failed to run the test .../runner/work/npmx.dev/npmx..../components/Input/Base.spec.ts.
Caused by: Caused by: Error: The iframe ".../runner/work/npmx.dev/npmx..../components/Input/Base.spec.ts" did not become ready within 60000ms. The tester likely failed to initialize, check the browser console for errors.

To view more test analytics, go to the Test Analytics Dashboard
📋 Got 3 mins? Take this short survey to help us improve Test Analytics.

@github-actions

github-actions Bot commented Sep 18, 2026 •
edited
Loading

Copy link
Copy Markdown

📊 Dependency Size Changes

Warning

This PR adds 3.1 MB of new dependencies, which exceeds the threshold of 200 kB.

📦 Package 📏 Size
[email protected] → [email protected] 1.5 MB
@napi-rs/[email protected] 1.4 MB
@json-render/[email protected] -914.8 kB
[email protected] -632.3 kB
[email protected] → [email protected] 603.4 kB
@nuxt/[email protected] → @nuxt/[email protected] 594.7 kB
@colordx/[email protected] → @colordx/[email protected] -546 kB
[email protected] -519.5 kB
[email protected] → [email protected] 475.2 kB
[email protected] -421.8 kB
@unhead/[email protected] → @unhead/[email protected] 410.6 kB
@devframes/[email protected] -355.2 kB
@nuxt/[email protected] -326.7 kB
@nuxt/[email protected] 326.1 kB
[email protected] → [email protected] 286.5 kB
[email protected] 266.3 kB
[email protected] 254.3 kB
[email protected] -212.4 kB
@nuxt/[email protected] -183.7 kB
@vitejs/[email protected] -174 kB
[email protected] 145.6 kB
[email protected] → [email protected] 136.6 kB
[email protected] 135 kB
[email protected] → [email protected] 134.1 kB
[email protected] 132.9 kB
@rollup/[email protected] → @rollup/[email protected] 123.1 kB
[email protected] → [email protected] 112.3 kB
[email protected] 111 kB
[email protected] 110.2 kB
@nuxt/[email protected] 110 kB
@nuxt/[email protected] -109.8 kB
@nuxt/[email protected] -108.1 kB
[email protected] -107.3 kB
@nuxt/[email protected] → @nuxt/[email protected] 99 kB
@nuxt/[email protected] 85.9 kB
[email protected] 83.6 kB
[email protected] 78.9 kB
[email protected] -78.4 kB
@bomb.sh/[email protected] -71.9 kB
[email protected] -70.6 kB
[email protected] -62.9 kB
[email protected] -56.4 kB
@devframes/[email protected] -48.4 kB
[email protected] → [email protected] 48.2 kB
[email protected] → [email protected] 48.1 kB
@nuxt/[email protected] → @nuxt/[email protected] 45.6 kB
[email protected] 42.6 kB
@csstools/[email protected] 41.2 kB
[email protected] → [email protected] 39.5 kB
[email protected] -38.9 kB
[email protected] 36.2 kB
[email protected] → [email protected] 35 kB
[email protected] → [email protected] 34.2 kB
[email protected] -32.4 kB
[email protected] -31.2 kB
[email protected] 30.5 kB
@nuxt/[email protected] → @nuxt/[email protected] 29.1 kB
[email protected] -29 kB
[email protected] -27.8 kB
@nuxt/[email protected] → @nuxt/[email protected] 27.6 kB
@babel/[email protected] → @babel/[email protected] 26 kB
[email protected] → [email protected] 25.1 kB
[email protected] -24.9 kB
@vue/[email protected] → @vue/[email protected] 23.9 kB
[email protected] → [email protected] 23.7 kB
@clack/[email protected] → @clack/[email protected] -22.6 kB
[email protected] 20.7 kB
@esbuild/[email protected] → @esbuild/[email protected] 20.5 kB
@vue/[email protected] → @vue/[email protected] 18.7 kB
[email protected] -18.7 kB
[email protected] -18.6 kB
[email protected] -18 kB
[email protected] -17.5 kB
[email protected] -16 kB
[email protected] -14.5 kB
[email protected] → [email protected] 13.1 kB
[email protected] → [email protected] 12.3 kB
[email protected] → [email protected] 11.8 kB
[email protected] -11.7 kB
[email protected] → [email protected] 11.5 kB
[email protected] -11.3 kB
[email protected] → [email protected] 11.3 kB
[email protected] -11.1 kB
[email protected] → [email protected] -11 kB
@vue/[email protected] → @vue/[email protected] 10.8 kB
[email protected] -10.7 kB
[email protected] -10.5 kB
@vue/[email protected] → @vue/[email protected] 10.3 kB
@clack/[email protected] → @clack/[email protected] -10.3 kB
@unhead/[email protected] → @unhead/[email protected] 10.2 kB
[email protected] → [email protected] 9.9 kB
[email protected] → [email protected] -9.3 kB
[email protected] -9.2 kB
[email protected] → [email protected] 9.1 kB
[email protected] 8.9 kB
[email protected] -8.5 kB
[email protected] 8.5 kB
[email protected] → [email protected] 8.4 kB
[email protected] -8.2 kB
[email protected] -7.7 kB
[email protected] → [email protected] 7.6 kB
@nuxt/[email protected] → @nuxt/[email protected] -7.5 kB
[email protected] -7.3 kB
[email protected] -7.3 kB
[email protected] → [email protected] -7.1 kB
[email protected] → [email protected] 7.1 kB
[email protected] -7 kB
[email protected] -6.7 kB
[email protected] -6.5 kB
[email protected] 6.2 kB
[email protected] -6 kB
[email protected] -6 kB
@vue/[email protected] → @vue/[email protected] 6 kB
[email protected] → [email protected] 5.5 kB
[email protected] -5.5 kB
[email protected] → [email protected] 5 kB
[email protected] -4.6 kB
[email protected] -4.5 kB
[email protected] → [email protected] 3.5 kB
@vue/[email protected] → @vue/[email protected] 3 kB
@dxup/[email protected] → @dxup/[email protected] 2.9 kB
[email protected] → [email protected] 2.5 kB
@vercel/[email protected] → @vercel/[email protected] 2.3 kB
@vue/[email protected] → @vue/[email protected] 2.1 kB
[email protected] → [email protected] 1.9 kB
[email protected] → [email protected] 1.9 kB
@nuxt/[email protected] → @nuxt/[email protected] 1.5 kB
[email protected] → [email protected] 1.4 kB
[email protected] → [email protected] 1.1 kB
[email protected] → [email protected] 949 B
[email protected] → [email protected] -453 B
[email protected] → [email protected] 408 B
@vitejs/[email protected] → @vitejs/[email protected] 352 B
@vue/[email protected] → @vue/[email protected] 351 B
[email protected] → [email protected] 316 B
@types/[email protected] → @types/[email protected] 162 B
[email protected] → [email protected] -157 B
@babel/[email protected] → @babel/[email protected] 152 B
[email protected] → [email protected] -47 B
[email protected] → [email protected] -39 B
@babel/[email protected] → @babel/[email protected] -24 B
[email protected] → [email protected] -23 B
@nuxt/[email protected] → @nuxt/[email protected] 0 B
@vue/[email protected] → @vue/[email protected] 0 B
[email protected] Unknown
[email protected] Unknown
[email protected] Unknown

Total size change: 3.1 MB

@socket-security

socket-security Bot commented Nov 1, 2026 •
edited
Loading

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Updated@​nuxt/​test-utils@​4.1.0 ⏵ 4.3.498 +110079 +194 +5100
Updatedvue@​3.5.42 ⏵ 3.5.449910091 +197100
Updatednuxt@​4.5.2 ⏵ 4.6.397100 +4100 +194 +1100
Updated@​clack/​prompts@​1.7.0 ⏵ 1.8.1100 +110010094100

View full report

@renovate

renovate Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

This branch had an error being deployed

1 failed and 1 active (outdated) deployments
Preview – npmx.dev — 40ff212b Deployed Nov 1, 2026 by vercel[bot]
View deployment
Preview – docs.npmx.dev — f6fc217d Deployed Nov 1, 2026 by vercel[bot]
View deployment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

chore dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@gameroman