What nuxt/nuxt shipped
Written by FoxPlug from the repository's own releases; not affiliated with Nuxt. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/nuxt/nuxt; Nuxt did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of October 5, 2026
What shipped
- Nuxt v4.6.1 patch release shipped with fixes across vite, nuxt and nitro packages. Release
- Added a nosource sourcemap option for sourcemap.client and sourcemap.server that keeps file names and line mappings but omits original source code. Pull request #36534
- ServerFetch is now typed against server routes instead of returning a plain Response. Pull request #36543
- Fixed navigation handling so aborted or cancelled navigation preserves error state and 404 responses are skipped correctly. Pull request #36546
- Fixed a page transition that could start with no page to leave, which previously left the transition promise pending forever. Pull request #36535
- Fixed the nitroAutoImports flag so disabling it actually disables h3 and nitro presets instead of modules re-enabling imports. Pull request #36548
- Module dependencies now resolve from the declaring module, so modules can require explicit versions of other modules. Pull request #36542
- Added a finishColor prop to the loading bar so it can use a different color after loading finishes. Pull request #36533
- Added a nuxt.request tracing channel around the renderer's fetch so request spans work with any server builder. Pull request #36483
- Added dedicated documentation for the spa-loading-template.html file. Pull request #36537
Why it matters
This week brings a patch release plus a steady stream of fixes for navigation, typing and the experimental Vite server builder. Several changes make types stronger, from serverFetch to the global $fetch, and reduce friction in dev for module authors and tools like pnpm global virtual stores.
Changelog entry
- V4.6.1 patch release. Release
- Add nosource sourcemap option for client and server. Pull request #36534
- Type serverFetch against server routes. Pull request #36543
- Type the global $fetch with Nuxt's TypedFetch. Pull request #36492
- Add nuxt.request tracing channel. Pull request #36483
- Add finishColor prop to the loading bar. Pull request #36533
- Preserve error state on aborted or cancelled navigation. Pull request #36546
- Don't start a page transition with no page to leave. Pull request #36535
- Only disable h3 and nitro presets when nitroAutoImports is off. Pull request #36548
- Resolve module dependencies from the declaring module. Pull request #36542
- Add spa-loading-template documentation. Pull request #36537
- Use the configured outDir as the public directory for the non-ssr environment. Pull request #36501
Nuxt v4.6.1 is out. This week: nosource sourcemaps, typed serverFetch, the global $fetch typed with Nuxt's TypedFetch, a nuxt.request tracing channel, a finishColor prop on the loading bar, and fixes across navigation, nitro and the Vite server builder.
Nuxt v4.6.1 has shipped, and this week's changes cover types, dev tooling and navigation. A new nosource option for client and server sourcemaps keeps file names and line mappings while leaving out original source code. serverFetch is now typed against server routes, and the global $fetch is typed with Nuxt's TypedFetch. There is a new nuxt.request tracing channel so request spans work with any server builder, plus a finishColor prop for the loading bar. Fixes landed for aborted or cancelled navigation, page transitions with no page to leave, the nitroAutoImports flag, module dependency resolution and the experimental Vite server builder.
Week of September 28, 2026
What shipped
- API routes now consistently return JSON errors and page rendering errors return HTML, improving error caching by removing user-agent based distinctions. Pull request #36455
- Async layouts are now awaited before navigation completes, fixing potential timing issues when layouts load asynchronously. Pull request #36454
- Kit now exports resolveServerVariant and addServerImports utilities to help module authors migrate to nuxt/server. Pull request #36445
- Compile error overlays now display on client-only pages by introducing a new nuxt:dev:error:ready hook that fires after the error handler is registered. Pull request #36444
- Tracing channels are now exposed for hooks, bundler plugins, transforms, and Nuxt middleware to help debug performance and plugin behavior. Pull request #36423
- Fixed a bug where disposing a page using useNuxtData() would incorrectly modify newer data entries for the same key. Pull request #36436
- Error responses on the dev server now preserve cookies and return JSON to JSON clients. Pull request #36451
- Nitro v2-style code detection now ignores type imports and logs when user code relies on deprecated patterns. Pull request #36442
- Route-less handlers in Nitro are now registered as global middleware for better v2 compatibility. Pull request #36441
- Package detection now uses package-manager-detector instead of relying on corepack, improving compatibility with Node 20+. Pull request #36434
Why it matters
This week addresses several stability issues in async handling, error reporting, and dev server behavior. The improvements to error responses and async layout handling reduce timing-related bugs, while new tracing channels and module utilities help developers debug and extend Nuxt more effectively.
Changelog entry
- Fix: render html page errors + json server route errors - api routes return json, page rendering returns html Pull request #36455
- Fix: await async layouts before navigation Pull request #36454
- Fix: leave a newer async data entry alone when an old one is taken off Pull request #36436
- Fix: show compile error overlay on client-only pages with nuxt:dev:error:ready hook Pull request #36444
- Fix: keep cookies + respond to json clients on errors Pull request #36451
- Feat: add resolveServerVariant + addServerImports variant support to kit Pull request #36445
- Feat: add hook, bundler and middleware tracing channels Pull request #36423
- Feat: improve scanning + reporting for nitro v2-style code Pull request #36442
- Fix: register route-less handlers as global middleware Pull request #36441
- Perf: use package-manager-detector to install packages Pull request #36434
- Docs: return streams directly in sendStream Pull request #36449
This week: better error handling for APIs vs pages, async layout timing fixes, improved dev error overlays, and new tracing for debugging hooks and bundler plugins.
Fresh updates to Nuxt this week focus on stability and developer experience. Error responses now correctly differentiate between JSON APIs and HTML pages for better caching. Async layouts properly await before navigation. Dev error overlays now work on client-only pages. New tracing channels expose hook, bundler, and middleware behavior. Kit adds utilities for module authors. Plus Nitro v2 compatibility improvements and better package manager detection.
Week of September 21, 2026
What shipped
- Added addon support to createUseFetch and createUseAsyncData to extend fetching capabilities. Pull request #35797
- Introduced a unified client prefetch scheduler to consistently handle prefetching across route chunks, components, and islands. Pull request #36391
- Added top-level prerender option as an alias for nitro.prerender for easier configuration. Pull request #32356
- Unmatched public asset paths are now served on client-side navigation instead of failing. Pull request #36169
- Dev SSR stacktraces and render errors are now mapped with source maps for better debugging. Pull request #36258
- Component imports are now refreshed after rename to prevent stale references. Pull request #36165
- Type preservation is now maintained when building into a relocated build directory. Pull request #36418
- Peer dependency ranges were widened to match the versions actually required by the framework. Pull request #36417
- Browser notices without errors no longer trigger the dev overlay in development mode. Pull request #36415
Why it matters
This week focused on improving developer experience through better error handling, unified prefetch scheduling, and more intuitive configuration patterns. Several fixes address edge cases in routing, type preservation, and component resolution that improve reliability in real-world applications.
Changelog entry
- Feat(nuxt): add addon support to createUseFetch and createUseAsyncData Pull request #35797
- Feat(nuxt): unified client prefetch scheduler Pull request #36391
- Feat(nuxt,vite-server): render the error page in the renderer itself Pull request #36399
- Feat(nuxt,schema): add top-level prerender alias for nitro.prerender Pull request #32356
- Feat(nuxt): serve unmatched public asset paths on client-side navigation Pull request #36169
- Feat(nitro,vite): map dev ssr stacktraces and render errors with source maps Pull request #36258
- Fix(nuxt): refresh component imports after rename Pull request #36165
- Fix(kit,nuxt): preserve types when building into a relocated build dir Pull request #36418
- Fix(kit): widen peer dependency ranges to supported versions Pull request #36417
- Fix(nuxt): skip browser notices without error in dev overlay Pull request #36415
- Fix(schema): deprecate nitro.* options duplicated at the top level Pull request #36416
- Fix(vite): pre-bundle deps of layers installed in
node_modulesPull request #36208
Fresh batch of improvements: better error pages, unified prefetch scheduling, component refresh fixes, and source map support for dev debugging. Plus easier prerender config and extended addon capabilities.
This week's updates to Nuxt bring meaningful improvements to developer experience. New addon support for fetch utilities, unified prefetch scheduling across components and routes, and direct error page rendering eliminate unnecessary requests. Developers benefit from better source map support for SSR debugging, fixed component refresh on rename, and more intuitive configuration options. These changes address both common friction points and edge cases in production applications.