@nuxt/rspack-builder
4.6.4 · 2 Nov 2026MIT590 / weekRepositoryHomepagenpmAtom feed
67 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 3.x
3.17.4
20 May 2025- Removed
schema: Remove nitro options from
DeepPartial Refactor Array.includes checks to use Sets
rspack: Use
ts-checker-rspack-plugin
3.17.4 is a regularly-scheduled patch release.
Upgrading
Our recommendation for upgrading is to run:
npx nuxi@latest upgrade --dedupe
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
Changelog
Performance
Refactor Array.includes checks to use Sets
Fixes
rspack: Use
ts-checker-rspack-plugin- Removed
schema: Remove nitro options from
DeepPartial
3.17.3
12 May 2025Our recommendation for upgrading is to run:
3.17.3 is a regularly-scheduled patch release.
Upgrading
Our recommendation for upgrading is to run:
npx nuxi@latest upgrade --dedupe
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
Changelog
3.17.2
5 May 2025Our recommendation for upgrading is to run:
3.17.2 is a regularly-scheduled patch release.
Upgrading
Our recommendation for upgrading is to run:
npx nuxi@latest upgrade --dedupe
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
Changelog
3.17.1
29 Apr 2025Our recommendation for upgrading is to run:
3.17.1 is the next patch release.
Upgrading
Our recommendation for upgrading is to run:
npx nuxi@latest upgrade --dedupe
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
Changelog
3.17.0
27 Apr 2025hideDelay: Controls how long to wait before hiding the loading barresetDelay: Controls how long to wait before resetting loading indicator stateWarning when server components don't have a root element #31365
Highlights
This release brings a major reworking of the async data layer, a new built-in component, better warnings, and performance improvements!
Data Fetching Improvements
A major reorganization of Nuxt's data fetching layer brings significant improvements to
useAsyncDataanduseFetch.Although we have aimed to maintain backward compatibility and put breaking changes behind the
experimental.granularCachedDataflag (disabled by default), we recommend testing your application thoroughly after upgrading. You can also disableexperimental.purgeCachedDatato revert to the previous behavior if you are relying on cached data being available indefinitely after components usinguseAsyncDataare unmounted.👉 Read the the original PR for full details (#31373), but here are a few highlights.
Consistent Data Across Components
All calls to
useAsyncDataoruseFetchwith the same key now share the underlying refs, ensuring consistency across your application:<!-- ComponentA.vue --> <script setup> const { data: users, pending } = useAsyncData('users', fetchUsers) </script> <!-- ComponentB.vue --> <script setup> // This will reference the same data state as ComponentA const { data: users, status } = useAsyncData('users', fetchUsers) // When either component refreshes the data, both will update consistently </script>This solves various issues where components could have inconsistent data states.
Reactive Keys
You can now use computed refs, plain refs, or getter functions as keys:
const userId = ref('123') const { data: user } = useAsyncData( computed(() => `user-${userId.value}`), () => fetchUser(userId.value) ) // Changing the userId will automatically trigger a new data fetch // and clean up the old data if no other components are using it userId.value = '456'Optimized Data Refetching
Multiple components watching the same data source will now trigger only a single data fetch when dependencies change:
// In multiple components: const { data } = useAsyncData( 'users', () => $fetch(`/api/users?page=${route.query.page}`), { watch: [() => route.query.page] } ) // When route.query.page changes, only one fetch operation will occur // All components using this key will update simultaneouslyBuilt-In Nuxt Components
<NuxtTime>- A new component for safe time displayWe've added a new
<NuxtTime>component for SSR-safe time display, which resolves hydration mismatches when working with dates (#31876):<template> <NuxtTime :datetime="Date.now()" /> </template>
The component accepts multiple time formats and gracefully handles both client and server rendering.
Enhanced
<NuxtErrorBoundary>The
<NuxtErrorBoundary>component has been converted to a Single File Component and now exposeserrorandclearErrorfrom the component - as well as in the error slot types, giving you greater ability to handle errors in your templates and viauseTemplateRef(#31847):<NuxtErrorBoundary @error="handleError"> <template #error="{ error, clearError }"> <div> <p>{{ error.message }}</p> <button @click="clearError">Try again</button> </div> </template> <!-- Content that might error --> <MyComponent /> </NuxtErrorBoundary>Router Improvements
<NuxtLink>now accepts atrailingSlashprop, giving you more control over URL formatting (#31820):<NuxtLink to="/about" trailing-slash>About</NuxtLink> <!-- Will render <a href="/about/"> -->
Loading Indicator Customization
You can now customize the loading indicator with new props directly on the component (#31532):
hideDelay: Controls how long to wait before hiding the loading barresetDelay: Controls how long to wait before resetting loading indicator state
<template> <NuxtLoadingIndicator :hide-delay="500" :reset-delay="300" /> </template>
Documentation as a Package
The Nuxt documentation is now available as an npm package! You can install
@nuxt/docsto access the raw markdown and YAML content used to build the documentation website (#31353).Developer Experience Improvements
We've added several warnings to help catch common mistakes:
Warning when server components don't have a root element #31365
Warning when using the reserved
runtimeConfig.appnamespace #31774Warning when core auto-import presets are overridden #29971
Error when
definePageMetais used more than once in a file #31634
Enhanced Module Development
Module authors will be happy to know:
A new
experimental.enforceModuleCompatibilityallows Nuxt to throw an error when a module is loaded that isn't compatible with it (#31657). It will be enabled by default in Nuxt v4.You can now automatically register every component exported via named exports from a file with
addComponentExports#27155
Performance Improvements
Several performance improvements have been made:
Switched to
tinyglobbyfor faster file globbing #31668Excluded
.datadirectory from type-checking for faster builds #31738Improved tree-shaking by hoisting the
purgeCachedDatacheck #31785
Upgrading
Our recommendation for upgrading is to run:
npx nuxi@latest upgrade --dedupe
This refreshes your lockfile and pulls in all the latest dependencies that Nuxt relies on, especially from the unjs ecosystem.
Changelog
Performance
kit,rspack,webpack: Switch to
tinyglobbynuxt: Remove
oxc-parsermanual wasm fallback logicnuxt: Remove unecessary type check for useFetch
3.16.2
1 Apr 2025nuxt: Improve tree-shaking of
useRequestEventon clientnuxt: Pass down attrs to
<Body>and<Html>nuxt: Use greedy catchall when
/indexis the last segment
3.16.2 is the next patch release.
Upgrading
Our recommendation for upgrading is to run:
npx nuxi@latest upgrade --dedupe
This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
Changelog
Performance
nuxt: Improve tree-shaking of
useRequestEventon client
Fixes
nuxt: Pass down attrs to
<Body>and<Html>nuxt: Use greedy catchall when
/indexis the last segmentnuxt: Reset
page:loading:endhook before navigationnuxt: Write initial cookie value if different from
document.cookienuxt: Support template string quotes in
resolveComponentnuxt: Show fatal errors thrown in middleware
nuxt: Use name to index route providers in dev
nuxt: Improve default scroll behaviour
vite: Return 404 for non-existent
_nuxt/paths in developmentnuxt: Pass error data to
error.vuenuxt: Use
unheadv2 api in default welcome + error pagesnuxt: Improve consistency of page metadata extraction
nuxt: Do not remove meta when
scanPageMetais disabled
3.16.1
19 Mar 2025nuxt: Use browser cache for payloads
nuxt: Restore nuxt aliases to nitro compilerOptions.paths
nuxt: Use new
mocked-exports
Performance
nuxt: Use browser cache for payloads
Fixes
nuxt: Restore nuxt aliases to nitro compilerOptions.paths
nuxt: Use new
mocked-exportsnuxt: Check resolved options for polyfills
nuxt: Render style component html
nuxt: Add missing lazy hydration prop in regex
nuxt: Fully resolve nuxt dependencies
vite: Don't show interim vite build output files
nuxt: Ignore prerendering unprefixed public assets
nuxt: Use more performant router catchall pattern
nuxt: Prevent param duplication in
typedPagesimplementationnuxt: Sort route paths before creating route tree
3.16.0
7 Mar 2025For Nuxt 3 users, we're shipping a legacy compatibility build so nothing breaks
The context implementation is now more direct via Nuxt itself
Import from Nuxt's auto-imports or
#app/composables/headinstead of@unhead/vue
Highlights
There's a lot in this one!
A New New Nuxt
Say hello to
create-nuxt, a new tool for starting Nuxt projects (big thanks to @devgar for donating the package name)!It's a streamlined version of
nuxi init- just a sixth of the size and bundled as a single file with all dependencies inlined, to get you going as fast as possible.Starting a new project is as simple as:
npm create nuxt
screenshot of create nuxt app
Special thanks to @cmang for the beautiful ASCII-art. ❤️
Want to learn more about where we're headed with the Nuxt CLI? Check out our roadmap here, including our plans for an interactive modules selector.
Unhead v2
We've upgraded to
unheadv2, the engine behind Nuxt's<head>management. This major version removes deprecations and improves how context works:For Nuxt 3 users, we're shipping a legacy compatibility build so nothing breaks
The context implementation is now more direct via Nuxt itself
// Nuxt now re-exports composables while properly resolving the context export function useHead(input, options = {}) { const unhead = injectHead(options.nuxt) return head(input, { head: unhead, ...options }) }If you're using Unhead directly in your app, keep in mind:
Import from Nuxt's auto-imports or
#app/composables/headinstead of@unhead/vueImporting directly from
@unhead/vuemight lose async context
Don't worry though - we've maintained backward compatibility in Nuxt 3, so most users won't need to change anything!
If you've opted into
compatibilityVersion: 4, check out our upgrade guide for additional changes.Devtools v2 Upgrade
Nuxt Devtools has leveled up to v2 (#30889)!
You'll love the new features like custom editor selection, Discovery.js for inspecting resolved configs (perfect for debugging), the return of the schema generator, and slimmer dependencies.
One of our favorite improvements is the ability to track how modules modify your Nuxt configuration - giving you X-ray vision into what's happening under the hood.
👉 Discover all the details in the Nuxt DevTools release notes.
Performance Improvements
We're continuing to make Nuxt faster, and there are a number of improvements in v3.16:
Using
exsolvefor module resolution (#31124) along with the rest of the unjs ecosystem (nitro, c12, pkg-types, and more) - which dramatically speeds up module resolutionSmarter module resolution paths (#31037) - prioritizes direct imports for better efficiency
Eliminated duplicated Nitro alias resolution (#31088) - leaner file handling
Streamlined
loadNuxtby skipping unnecessary resolution steps (#31176) - faster startupsAdopt
oxc-parserfor parsing in Nuxt plugins
All these speed boosts happen automatically - no configuration needed!
Shout out to CodSpeed with Vitest benchmarking to measure these improvements in CI - it has been really helpful.
To add some anecdotal evidence, my personal site at roe.dev loads 32% faster with v3.16, and nuxt.com is 28% faster. I hope you see similar results! ⚡️
Delayed Hydration Support
We're very pleased to bring you native delayed/lazy hydration support (#26468)! This lets you control exactly when components hydrate, which can improve initial load performance and time-to-interactive. We're leveraging Vue's built-in hydration strategies - check them out in the Vue docs.
<template> <!-- Hydrate when component becomes visible in viewport --> <LazyExpensiveComponent hydrate-on-visible /> <!-- Hydrate when browser is idle --> <LazyHeavyComponent hydrate-on-idle /> <!-- Hydrate on interaction (mouseover in this case) --> <LazyDropdown hydrate-on-interaction="mouseover" /> <!-- Hydrate when media query matches --> <LazyMobileMenu hydrate-on-media-query="(max-width: 768px)" /> <!-- Hydrate after a specific delay in milliseconds --> <LazyFooter :hydrate-after="2000" /> </template>
You can also listen for when hydration happens with the
@hydratedevent:<LazyComponent hydrate-on-visible @hydrated="onComponentHydrated" />
Learn more about lazy hydration in our components documentation.
Advanced Pages Configuration
You can now fine-tune which files Nuxt scans for pages (#31090), giving you more control over your project structure:
export default defineNuxtConfig({ pages: { // Filter specific files or directories pattern: ['**/*.vue'], } })Enhanced Debugging
We've made debugging with the
debugoption more flexible! Now you can enable just the debug logs you need (#30578):export default defineNuxtConfig({ debug: { // Enable specific debugging features templates: true, modules: true, watchers: true, hooks: { client: true, server: true, }, nitro: true, router: true, hydration: true, } })Or keep it simple with
debug: trueto enable all these debugging features.Decorators Support
For the decorator fans out there (whoever you are!), we've added experimental support (#27672). As with all experimental features, feedback is much appreciated.
export default defineNuxtConfig({ experimental: { decorators: true } })function something (_method: () => unknown) { return () => 'decorated' } class SomeClass { @something public someMethod () { return 'initial' } } const value = new SomeClass().someMethod() // returns 'decorated'Named Layer Aliases
It's been much requested, and it's here! Auto-scanned local layers (from your
~~/layersdirectory) now automatically create aliases. You can access your~~/layers/testlayer via#layers/test(#30948) - no configuration needed.If you want named aliases for other layers, you can add a name to your layer configuration:
export default defineNuxtConfig({ $meta: { name: 'example-layer', }, })This creates the alias
#layers/example-layerpointing to your layer - making imports cleaner and more intuitive.Error Handling Improvements
We've greatly improved error messages and source tracking (#31144):
Better warnings for undefined
useAsyncDatacalls with precise file location informationError pages now appear correctly on island page errors
Plus, we're now using Nitro's beautiful error handling (powered by youch) to provide more helpful error messages in the terminal, complete with stacktrace support.
Nitro now also automatically applies source maps without requiring extra Node options, and we set appropriate security headers when rendering error pages.
Module Development Improvements
For module authors, we've added the ability to augment Nitro types with
addTypeTemplate(#31079):// Inside your Nuxt module export default defineNuxtModule({ setup(options, nuxt) { addTypeTemplate({ filename: 'types/my-module.d.ts', getContents: () => ` declare module 'nitropack' { interface NitroRouteConfig { myCustomOption?: boolean } } ` }, { nitro: true }) } })Nitro v2.11 Upgrade
We've upgraded to Nitro v2.11. There are so many improvements - more than I can cover in these brief release notes.
👉 Check out all the details in the Nitro v2.11.0 release notes.
New
unjsMajor VersionsThis release includes several major version upgrades from the unjs ecosystem, focused on performance and smaller bundle sizes through ESM-only distributions:
Unenv upgraded to v2 (full rewrite)
db0 upgraded to v0.3 (ESM-only, native node:sql, improvements)
Ohash upgraded to v2 (ESM-only, native node:crypto support, much faster)
Untyped upgraded to v2 (ESM-only, smaller install size)
Unimport upgraded to v4 (improvements)
c12 upgraded to v3 (ESM-only)
Pathe upgraded to v2 (ESM-only)
cookie-es upgraded to v2 (ESM-only)
Esbuild upgraded to v0.25
Chokidar upgraded to v4
Upgrading
As usual, our recommendation for upgrading is to run:
npx nuxi@latest upgrade --dedupe
This refreshes your lockfile and pulls in all the latest dependencies that Nuxt relies on, especially from the unjs ecosystem.
Changelog
Performance
nuxt: Remove duplicated nitro alias resolution
Fixes
nuxt: Remove
divwrapper in client-only pagesui-templates: Remove extra
<pre>when rendering dev errorsRemove unimplemented
page:transition:starttype
3.15.4
29 Jan 2025As usual, our recommendation for upgrading is to run:
3.15.4 is the next patch release.
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
3.15.3
24 Jan 2025Alongside a range of improvements, we've also shipped a significant fix to impose CORS origin restrictions on the dev server. This applies to your Vite or Webpack/Rspack dev middleware only.
3.15.3 is the next regularly scheduled patch release.
Highlights
CORS configuration for dev server
Alongside a range of improvements, we've also shipped a significant fix to impose CORS origin restrictions on the dev server. This applies to your Vite or Webpack/Rspack dev middleware only.
This is a significant/breaking change we would not normally ship in a patch but it is a security fix (see github.com/nuxt/nuxt/security/advisories/GHSA-4… and github.com/nuxt/nuxt/security/advisories/GHSA-2…) and we urge you to update ASAP.
You can configure the allowed origins and other CORS options via the
devServer.corsoptions in yournuxt.config, which may be relevant if you are developing with a custom hostname:export default defineNuxtConfig({ devServer: { cors: { origin: ['https://custom-origin.com'], }, }, })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
3.15.2
15 Jan 2025nuxt: Remove code duplication in client-only
nuxt: Use lighter
@nuxt/clidependencykit: Remove iterations when resolving module path
3.15.2 is the next regularly scheduled patch release.
Highlights
Startup performance improvements
It is worth noting that this release includes some pretty significant performance improvements which you should notice particularly in the startup time. In my tests in the nuxt monorepo,
fixture time to vite build complete (v3.15.1) time to vite build complete (v3.15.2) minimal 850ms 710ms everything bagel 3,021ms 1,690ms There's more improvement to do here but hopefully these are good numbers!
CLI refactor
To improve performance within Nuxt projects, we've published a new
@nuxt/clidistribution ofnuxi, which is used under-the-hood innuxt(see issue). This should behave exactly the same and nothing needs to be updated in your projects (for example, you will continue to use thenuxiornuxtcommands). The only significant change is that it no longer inlines dependencies. Feedback is welcome 🙏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
Performance
nuxt: Remove code duplication in client-only
nuxt: Use lighter
@nuxt/clidependencykit: Remove iterations when resolving module path
nuxt: Avoid checking fs for existence of scanned pages
nuxt: Defer version/config warnings to after build
Fixes
nuxt: Collect all identifiers before extracting page metadata
nuxt: Don't hoist identifiers declared locally in
definePageMetawhen extracting page metadatakit: Reorder
#buildto the end oftsConfigpathsnuxt: Use
fullPathinstead of empty string in router hmrRelax nuxt version constraints to current
nuxt: Add import protection for
@nuxt/clikit: Fully resolve plugin paths when normalising them
nuxt: Call
page:loading:endonly once with nested pagesnuxt: Warn about ignored char while parsing route segment
nuxt: Allow url-specific chars in vfs
nuxt: Do not warn about invalid characters in route groups/catchalls
vite: Provide fallback alias for
#app-manifestnuxt: Avoid invoking
shouldPrefetchon the server sidenuxt: Decode id before resolving relative imports
3.15.1
5 Jan 2025- Removed
nuxt: Drop
pathebrowser dep for deep server components nuxt: Skip experimental async context transform in client build
schema: Drop unneeded type-only schema dependencies
3.15.1 is the next regularly scheduled patch release.
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
Performance
nuxt: Skip experimental async context transform in client build
schema: Drop unneeded type-only schema dependencies
rspack,webpack: Drop
lodash-esdependency- Removed
nuxt: Drop
pathebrowser dep for deep server components
Fixes
nuxt: Update module path for defaults
nuxt: Ignore non-reference identifiers when extracting page metadata
nuxt: Pass
nuxtinstance toresolvePagesRoutesschema: Support pfx certificate for dev server
nuxt: Use node
locationinstead ofrangefor route meta property extractionschema: Override
vueCompilerOptions.pluginstypenuxt: Respect
baseURLwhen ignoring prerendered manifestnuxt: Respect
router.optionswhen hmring routes
3.15.0
24 Dec 2024kit: Allow module default options to be async
nuxt: Add new types to vue preset
nuxt: Experimental
extraPageMetaExtractionKeys
Highlights
Snowfall!
Happy holidays! You'll notice when you start Nuxt that (if you're in the Northern Hemisphere) there's some snow on the loading screen (#29871).
Vite 6 included
Nuxt v3.15 includes Vite 6 for the first time. Although this is a major version, we expect that this won't be a breaking change for Nuxt users (see full migration guide). However, please take care if you have dependencies that rely on a particular Vite version.
One of the most significant changes with Vite 6 is the new Environment API, which we hope to use in conjunction with Nitro to improve the server dev environment. Watch this space!
You can read the full list of changes in the Vite 6 changelog.
Chromium devtools improvements
We talk a lot about the Nuxt DevTools, but v3.15 ships with better integration in dev mode for Chromium-based browser devtools.
We now use the Chrome DevTools extensibility API to add support for printing nuxt hook timings in the browser devtools performance panel.
CleanShot 2024-11-14 at 15 05 22@2x
Navigation mode for
callOncecallOnceis a built-in Nuxt composable for running code only once. For example, if the code runs on the server it won't run again on the client. But sometimes you do want code to run on every navigation - just avoid the initial server/client double load. For this, there's a newmode: 'navigation'option that will run the code only once per navigation. (See #30260 for more info.)await callOnce(() => counter.value++, { mode: 'navigation' })HMR for templates, pages + page metadata
We now implement hot module reloading for Nuxt's virtual files (like routes, plugins, generated files) as well as for the content of page metadata (within a
definePageMetamacro) (#30113).This should mean you have a faster experience in development, as well as not needing to reload the page when making changes to your routes.
Page meta enhancements
We now support extracting extra page meta keys (likely used by module authors) via
experimental.extraPageMetaExtractionKeys(#30015). This enables module authors to use this information at build time, in thepages:resolvedhook.We also now support local functions in
definePageMeta(#30241). This means you can do something like this:function validateIdParam(route) { return !!(route.params.id && !isNaN(Number(route.params.id))) } definePageMeta({ validate: validateIdParam, })Performance improvements
We now preload the app manifest in the browser if it will be used when hydrating the app (#30017).
We'll also tree shake vue-router's hash mode history out of your bundle if we can - specifically, if you haven't customised your
app/router.options.ts(#30297).v4 updates
A few more changes shipped for the new defaults for v4, including only inlining styles by default for Vue components (#30305).
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
Enhancements
kit: Allow module default options to be async
nuxt: Add new types to vue preset
nuxt: Experimental
extraPageMetaExtractionKeysnuxt,schema: Allow setting serialisable vue app config
nuxt: Print nuxt hook timings in browser devtools
nuxt: Support vue directive auto-imports within unimport
schema: Add snow effect on loading screen in winter
nuxt: Support local functions in
definePageMetanuxt: Add
mode: 'navigation'tocallOnce
Performance
nuxt: Preload app manifest
nuxt: Use static
hashModeoptionvite: Use vite to clear screen
schema: Only inline styles for vue components
nuxt: Remove useId from composable key plugin
Fixes
nuxt: Check if nuxt link observer is null
nuxt: Unref the default value of asyncData when clearing
kit: Re-export
addServerTemplateRemove unused dependencies and tidy project
vite: Add back some dev-bundler dependencies
nuxt: Do not persist
extraExtractionKeyson runtimeroute.metanuxt: Allow array/object
stylevalue for head componentsnuxt: Tidy up remnants of previous
useIdimplementationkit,nuxt: Provide
buildDirtonormalizeTemplatekit: Add better logging for non-resolved modules
nuxt: Correct return type of
useRequestFetchnuxt,vite: Hmr for templates, pages + page metadata
nuxt: Use
nitropackrather thannitroimportkit: Use resolved module paths for transpile + modulesDir
Update
engines.nodeto match dependenciesschema: Allow
routerOptions.historyto return nullnuxt: Render client page directly when not hydrating
nuxt: Use
useIdfor island client component teleport idnuxt: De-default async layout components
nuxt: Correct types for
nuxtandnuxt/appnuxt,schema: Allow showing spa loader til after hydration
nuxt: Remove whitespace around spa loading template
nuxt: Hoist environment types
schema: Hoist nitro runtime types
nuxt: Ensure
getRouteRulesworks with nitro signaturenuxt: Respect
replacein middleware withnavigateTonuxt: Update import paths for
nitropacknuxt: Don't use
<RouterLink>for links starting with#vite: Ignore optimising
#app-manifestnuxt: Use
useIdforclient-fallbackcomponent uidschema: Gate inline style change behind v4 check
nuxt: Do not resolve deep imports for
@vitest/kit: Initialize tsconfig paths in
addTemplateif undefinednuxt: Treat client useAsyncData calls as async boundaries
nuxt: Initialise
import.meta.hot.data
3.14.1592
19 Nov 2024rspack: Update
webpackbarwith support for rspacknuxt: Assign default name to component without setup
kit: Use
dstto deduplicate templates when adding them
3.14.1592 is the next patch release.
Changelog
Fixes
rspack: Update
webpackbarwith support for rspacknuxt: Assign default name to component without setup
kit: Use
dstto deduplicate templates when adding themnuxt: Handle empty plugin files
vite: Use resolved nuxt template
dstto invalidate modulesnuxt: Return null map for empty plugin metadata
kit: Resolve module paths before appending subpaths
nuxt: Recompile templates on
changeeventsnuxt: Do not include
<NuxtWelcome>when buildingnuxt: Allow scanning metadata from 2+ files at same path
nuxt: Do not disallow importing nitro dependencies
3.14.159
6 Nov 2024nuxt: Update nitropack preset directory
kit: Fall back to meta version if there's no
module.jsonkit: Use
mllyto resolve module paths to avoid cjs fallback
3.14.159 is a hotfix release to address regressions in v3.14.
We're leaning into the π theme - future patch releases of this minor version will just continue adding digits. (Sorry for any inconvenience! 😆)
Changelog
Fixes
nuxt: Update nitropack preset directory
kit: Fall back to meta version if there's no
module.jsonkit: Use
mllyto resolve module paths to avoid cjs fallbackwebpack,rspack: Add adapter for
webpack-dev-middlewarenuxt: Remove null-byte prefix for virtual files
kit: Convert module path to file url before reading meta
3.12.2
4 Nov 2024nuxt: Remove backticks around runtimeConfig warning log
nuxt: Replace deprecated
app.rootIdwithapp.rootAttrs.id
3.12.2 is the a regularly scheduled patch release.
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
Fixes
nuxt: Remove backticks around runtimeConfig warning log
nuxt: Replace deprecated
app.rootIdwithapp.rootAttrs.id
- 0.0.x
0.0.0
24 Sep 2024
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.