Packages

@nuxt/rspack-builder

4.6.4 · 2 Nov 2026MIT590 / weekRepositoryHomepagenpmAtom feed

Your version

4.1.0

2 Sep 2025Where it was published

4.6.4 is the newest release of 4.x.

In short

11 new9 faster24 fixed44 internal

Security

Release note

Highlights

Build and Performance Improvements

Enhanced Chunk Stability

Build stability has been significantly improved with import maps (#33075). This prevents cascading hash changes that could invalidate large portions of your build when small changes are made:

<!-- Automatically injected import map -->
<script type="importmap">{"imports":{"#entry":"/_nuxt/DC5HVSK5.js"}}</script>

By default, JS chunks emitted in a Vite build are hashed, which means they can be cached immutably. However, this can cause a significant issue: a change to a single component can cause every hash to be invalidated, massively increasing the chance of 404s.

In short:

  1. A component is changed slightly - the hash of its JS chunk changes

  2. The page which uses the component has to be updated to reference the new file name

  3. The entry now has its hash changed because it dynamically imports the page

  4. every other file which imports the entry has its hash changed because the entry file name is changed

Obviously this wasn't optimal. With this new feature, the hash of (otherwise) unchanged files which import the entry won't be affected.

This feature is automatically enabled and helps maintain better cache efficiency in production. It does require native import map support, but Nuxt will automatically disable it if you have configured vite.build.target to include a browser that doesn't support import maps.

And of course you can disable it if needed:

export default defineNuxtConfig({
  experimental: {
    entryImportMap: false
  }
})

Experimental Rolldown Support

Nuxt now includes experimental support for rolldown-vite (#31812), bringing Rust-powered bundling for potentially faster builds.

To try Rolldown in your Nuxt project, you need to override Vite with the rolldown-powered version since Vite is a dependency of Nuxt. Add the following to your package.json:

npm:

{
  "overrides": {
    "vite": "npm:rolldown-vite@latest"
  }
}

pnpm:

{
  "pnpm": {
    "overrides": {
      "vite": "npm:rolldown-vite@latest"
    }
  }
}

yarn:

{
  "resolutions": {
    "vite": "npm:rolldown-vite@latest"
  }
}

bun:

{
  "overrides": {
    "vite": "npm:rolldown-vite@latest"
  }
}

After adding the override, reinstall your dependencies. Nuxt will automatically detect when Rolldown is available and adjust its build configuration accordingly.

For more details on Rolldown integration, see the Vite Rolldown guide.

Note

This is experimental and may have some limitations, but offers a glimpse into the future of high-performance bundling in Nuxt.

Improved Lazy Hydration

Lazy hydration macros now work without auto-imports (#33037), making them more reliable when component auto-discovery is disabled:

<script setup>
// Works even with components: false
const LazyComponent = defineLazyHydrationComponent(
  'visible',
  () => import('./MyComponent.vue')
)
</script>

This ensures that components that are not "discovered" through Nuxt (e.g., because components is set to false in the config) can still be used in lazy hydration macros.

Enhanced Page Rules

If you have enabled experimental extraction of route rules, these are now exposed on a dedicated rules property on NuxtPage objects (#32897), making them more accessible to modules and improving the overall architecture:

// In your module
nuxt.hook('pages:extend', pages => {
  pages.push({
    path: '/api-docs',
    rules: { 
      prerender: true,
      cors: true,
      headers: { 'Cache-Control': 's-maxage=31536000' }
    }
  })
})

The defineRouteRules function continues to work exactly as before, but now provides better integration possibilities for modules.

Module Development Enhancements

Module Dependencies and Integration

Modules can now specify dependencies and modify options for other modules (#33063). This enables better module integration and ensures proper setup order:

export default defineNuxtModule({
  meta: {
    name: 'my-module',
  },
  moduleDependencies: {
    'some-module': {
      // You can specify a version constraint for the module
      version: '>=2',
      // By default moduleDependencies will be added to the list of modules 
      // to be installed by Nuxt unless `optional` is set.
      optional: true,
      // Any configuration that should override `nuxt.options`.
      overrides: {},
      // Any configuration that should be set. It will override module defaults but
      // will not override any configuration set in `nuxt.options`.
      defaults: {}
    }
  },
  setup (options, nuxt) {
    // Your module setup logic
  }
})

This replaces the deprecated installModule function and provides a more robust way to handle module dependencies with version constraints and configuration merging.

Module Lifecycle Hooks

Module authors now have access to two new lifecycle hooks: onInstall and onUpgrade (#32397). These hooks allow modules to perform additional setup steps when first installed or when upgraded to a new version:

export default defineNuxtModule({
  meta: {
    name: 'my-module',
    version: '1.0.0',
  },

  onInstall(nuxt) {
    // This will be run when the module is first installed
    console.log('Setting up my-module for the first time!')
  },

  onUpgrade(inlineOptions, nuxt, previousVersion) {
    // This will be run when the module is upgraded
    console.log(`Upgrading my-module from v${previousVersion}`)
  }
})

The hooks are only triggered when both name and version are provided in the module metadata. Nuxt uses the .nuxtrc file internally to track module versions and trigger the appropriate hooks. (If you haven't come across it before, the .nuxtrc file should be committed to version control.)

Tip

This means module authors can begin implementing their own 'setup wizards' to provide a better experience when some setup is required after installing a module.

Enhanced File Resolution

The new ignore option for resolveFiles (#32858) allows module authors to exclude specific files based on glob patterns:

// Resolve all .vue files except test files
const files = await resolveFiles(srcDir, '**/*.vue', {
  ignore: ['**/*.test.vue', '**/__tests__/**']
})

Layer Directories Utility

A new getLayerDirectories utility (#33098) provides a clean interface for accessing layer directories without directly accessing private APIs:

import { getLayerDirectories } from '@nuxt/kit'

const layerDirs = await getLayerDirectories(nuxt)
// Access key directories:
// layerDirs.app        - /app/ by default
// layerDirs.appPages   - /app/pages by default
// layerDirs.server     - /server by default
// layerDirs.public     - /public by default

Developer Experience Improvements

Simplified Kit Utilities

Several kit utilities have been improved for better developer experience:

  • addServerImports now supports single imports (#32289):

// Before: required array
addServerImports([{ from: 'my-package', name: 'myUtility' }])

// Now: can pass directly
addServerImports({ from: 'my-package', name: 'myUtility' })

Performance Optimizations

This release includes several internal performance optimizations:

  • Improved route rules cache management

  • Optimized app manifest watching

  • Better TypeScript processing for page metadata

Notable Fixes

  • Improved useFetch hook typing

  • Better handling of TypeScript expressions in page metadata (#32902, #32914)

  • Enhanced route matching and synchronization

  • Reduced verbosity of Vue server warnings in development

  • Better handling of relative time calculations in <NuxtTime>

Upgrading

As usual, our recommendation for upgrading is to run:

npx nuxt upgrade --dedupe

This will refresh your lockfile and pull in all the latest dependencies that Nuxt relies on, especially from the unjs ecosystem.

Changelog

compare changes

Enhancements

  • kit: Add ignore option to resolveFiles

  • kit: Add onInstall and onUpgrade module hooks

  • nuxt,vite: Add experimental support for rolldown-vite

  • nuxt: Extract defineRouteRules to page rules property

  • nuxt,vite: Use importmap to increase chunk stability

  • nuxt: Lazy hydration macros without auto-imports

  • kit,nuxt,schema: Allow modules to specify dependencies

  • kit,nuxt: Add getLayerDirectories util and refactor to use it

Performance

  • nuxt: Clear inline route rules cache when pages change

  • nuxt: Stop watching app manifest once a change has been detected

Fixes

  • nuxt: Handle satisfies in page augmentation

  • nuxt: Type response in useFetch hooks

  • nuxt: Add TS parenthesis and as expression for page meta extraction

  • nuxt: Use correct unit thresholds for relative time

  • nuxt: Handle uncached current build manifests

  • kit: Resolve directories in resolvePath and normalize file extensions

  • schema,vite: Bump requestTimeout + allow configuration

  • nuxt: Deep merge extracted route meta

  • nuxt: Do not expose app components until fully resolved

  • kit: Only exclude node_modules/ if no custom srcDir

  • nuxt: Transform ts before page meta extraction

  • nuxt: Compare final matched routes when syncing route object

  • nuxt: Make vue server warnings much less verbose in dev mode

  • schema: Allow disabling cssnano/autoprefixer postcss plugins

  • kit: Ensure local layers are prioritised alphabetically

  • kit,nuxt: Expose global types to vue compiler

  • deps: Bump devalue

  • nuxt: Support config type inference for defineNuxtModule().with()

  • nuxt: Search for colliding names in route children

  • nuxt: Delete nuxtApp._runningTransition on resolve

  • nuxt: Add validation for nuxt island reviver key

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.