Skip to content

chore(deps): update nuxt framework to v4 - #94

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-nuxt
Open

chore(deps): update nuxt framework to v4#94
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-nuxt

Conversation

@renovate

@renovate renovate Bot commented Jul 16, 2025 •
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/kit (source) ^3.11.2 → ^4.6.4 age confidence
nuxt (source) ^2.17.3 → ^4.6.4 age confidence
nuxt (source) ^3.11.2 → ^4.6.4 age confidence

Release Notes

nuxt/nuxt (@​nuxt/kit)

v4.6.4

Compare Source

4.6.4 is a security release. It fixes eight advisories in Nuxt and pulls in nitropack 2.13.6, which fixes three more in Nitro. We recommend upgrading as soon as you can.

⚠️ Behaviour changes

These probably won't affect most apps, but it's worth flagging anyway:

  1. Error details in production. When a page fails to render on the server, the error page and the payload now only carry message and data of errors you create with createError. Everything else is stripped.
  2. Dev server Host checks. Webpack and rspack dev servers now reject requests with an unexpected Host header, as Vite already does. If you use a custom hostname or tunnel, you'll need to add it to the new devServer.allowedHosts option.
  3. workspaceDir detection. When workspaceDir isn't set, Nuxt now only widens it past rootDir to an explicit workspace root or the closest git repository.
  4. Nitropack cached routes. cache, swr and isr route rules now only cache GET and HEAD requests, and no longer store responses that set a cookie or send Cache-Control: private or no-store. Wildcard proxy and redirect rules also reject requests whose resolved target would leave the rule's scope.
  5. Route rules and encoded slashes. Route rules now match paths that contain encoded slashes, so /api%2Fadmin is covered by a /api/** rule.

👉 Changelog

compare changes

🩹 Fixes
  • nitro,nuxt: require unrouting 0.3.2 (768d21368)
  • nitro: preserve wildcard tails in case-insensitive route rules (bf31e4cd8)
  • nitro: require nitropack 2.13.6 (1b13c6981)
  • nitro: keep leading double slash in renderer request path (75c12c6fb)
  • nuxt: use unambiguous encoding for island hash (6f1b93c64)
  • vite-server: resolve wildcard redirect tails from the matched segments (1e7dfa6a7)
  • nuxt: do not expose details of untrusted thrown errors (8c56b71e4)
  • nuxt: strip trailing slashes in linear time (97424dd21)
  • nitro,webpack: include hosts the CLI allows after loading the config (8c11d965d)
  • webpack: skip hot middleware for forbidden dev requests (3c9645326)
  • rspack,webpack: reject unexpected Host headers in dev middleware (f8d64c9aa)
  • schema,nitro,vite: add devServer.allowedHosts (3e1c7964e)
  • nitro,nuxt: match route rules for paths with encoded slashes (084396b10)
  • schema: only widen workspace dir to a declared workspace root (89d3306d1)
  • nitro: only trust x-forwarded-proto in when opted-in (#​36818)
  • nitro: stream the body read through a nuxt/server handler (#​36817)
  • kit: suggest the specific fix when loading falls back to jiti (24d75659d)
  • vite: use a single type checker (#​36774)
  • nitro,vite: remove windows + virtual dev ssr css links after hydration (#​36765)
  • nitro,vite: dedupe dev css by module node (#​36420)
  • nuxt: avoid hoisting setup-only values from definePageMeta (#​36751)
  • nuxt: only match hydration modifiers after lazy prefix (#​36750)
  • kit,nitro,nuxt: make emitted tsconfig/types stable across reruns (#​36747)
  • nuxt: render inlined component styles after stylesheet links (#​36714)
  • webpack: use valid devtool for hidden client sourcemaps in dev (#​36555)
📖 Documentation
  • clarify template dependency regeneration (#​36766)
  • revise README structure and headings (#​36772)
  • link the Nuxt DevTools docs on nuxt.com (#​36769)
  • warn against spreading untrusted objects onto server components (1225ca7ff)
  • update anchors for flat heading ids (#​36664)
🏡 Chore
  • add 1000-row listing routes to the benchmark (c852d871f)
  • add client page weight and browser timing suites (#​36788)
✅ Tests
🤖 CI
  • check unversioned docs links against branch docs version (d093c88b1)
  • skip unneeded checks for release prs (4b90681bd)
  • skip benchmarks in merge groups (6428070e0)
  • re-enable codspeed ⚡ (bc17c03d1)
❤️ Contributors

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](https://redirect.github.com/nuxt/nuxt

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

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Every minute (* * * * *)
  • 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.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • 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 force-pushed the renovate/major-nuxt branch from 7bda245 to 4ac065e Compare July 21, 2025 15:06
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch from 4ac065e to 1bebe78 Compare July 29, 2025 01:04
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 2 times, most recently from 5e68aa9 to fd891d2 Compare August 10, 2025 15:14
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 2 times, most recently from 6a7be5c to 01bff88 Compare August 19, 2025 11:55
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 3 times, most recently from e4a9c98 to 1c37039 Compare September 6, 2025 03:12
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch from 1c37039 to 6434092 Compare September 13, 2025 10:58
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch from 6434092 to cae28ef Compare September 25, 2025 17:36
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch from cae28ef to 0322473 Compare October 6, 2025 19:15
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 2 times, most recently from 1a53657 to 2ddc232 Compare October 25, 2025 06:44
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 2 times, most recently from a2d5def to e7eca6a Compare November 10, 2025 22:40
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch from e7eca6a to 583139d Compare November 18, 2025 23:27
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 2 times, most recently from dbee016 to 918a622 Compare December 9, 2025 17:49
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch from 918a622 to 69eb031 Compare December 31, 2025 18:33
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch from 69eb031 to 870fbdb Compare January 8, 2026 21:12
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 3 times, most recently from 7b8498c to b77d49a Compare January 23, 2026 20:59
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 2 times, most recently from d751777 to d4c1dcd Compare February 7, 2026 18:12
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 2 times, most recently from 918b021 to 93d3568 Compare February 17, 2026 18:19
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 2 times, most recently from 2f148ac to 6f45a26 Compare March 12, 2026 15:01
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 2 times, most recently from 4dab2f5 to 1c3fdd2 Compare June 3, 2026 17:38
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 2 times, most recently from 5f6fcd1 to b5c9b08 Compare June 11, 2026 22:51
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 3 times, most recently from b111b41 to 1156c69 Compare July 18, 2026 22:40
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 3 times, most recently from 85a4ee6 to f9fc161 Compare July 27, 2026 12:06
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 2 times, most recently from a935ae9 to 3f4d889 Compare August 5, 2026 16:52
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 2 times, most recently from d7753a0 to e6ee2d9 Compare August 14, 2026 21:52
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch from e6ee2d9 to 9f1e3a8 Compare August 26, 2026 10:47
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 5 times, most recently from e4fa91d to c3c209d Compare September 9, 2026 13:53
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 2 times, most recently from 2a8191a to 2a8566c Compare September 15, 2026 10:13
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 2 times, most recently from 8bd1d67 to 395ebb0 Compare September 30, 2026 23:52
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 3 times, most recently from 4d36dd2 to d0a6d60 Compare October 11, 2026 04:23
@renovate
renovate Bot force-pushed the renovate/major-nuxt branch 2 times, most recently from b05e131 to eeaf827 Compare October 17, 2026 20:30
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

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@alessiochiffi