What nuxt/nuxt shipped
Written by FoxPlug from public releases; not affiliated with Nuxt. An automatic summary of the public release, pull request and commit data of github.com/nuxt/nuxt. Nuxt did not write it and does not use or endorse FoxPlug. Every line links to the public change it describes.
Get a weekly update like this for your product, free
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
- Error pages now render directly in the renderer instead of making a second request to `/__nuxt_error`. Pull request #36399
- 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_modules` Pull 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.