Skip to content

chore(deps): update dependency @nuxt/kit to v4#6189

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-nuxtjs-monorepo
Open

chore(deps): update dependency @nuxt/kit to v4#6189
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-nuxtjs-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 24, 2026 •
edited
Loading

โ„น๏ธ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@nuxt/kit (source) ^3.12.0 โ†’ ^4.4.4 age adoption passing confidence

Release Notes

nuxt/nuxt (@โ€‹nuxt/kit)

v4.4.4

Compare Source

v4.4.2

Compare Source

v4.4.1

Compare Source

v4.3.1

Compare Source

4.3.1 is a regularly scheduled patch release.

๐Ÿ‘‰ Changelog

compare changes

๐Ÿฉน Fixes
  • nuxt: Correct reference format of server builder (#โ€‹34177)
  • nuxt: Add status/statusText getters to NuxtError (#โ€‹34188)
  • nuxt: Don't inject shared types for differing auto-imports (#โ€‹34191)
  • schema: Add direnv and vendor to default ignore (#โ€‹34190)
  • nuxt: Focus hash links after navigation (#โ€‹34193)
  • nuxt: Exclude head runtime from unhead imports transform (#โ€‹34195)
  • kit: Include prereleases in semver satisfy check (#โ€‹34210)
  • nitro: Encode unicode paths in x-nitro-prerender header (#โ€‹34202)
  • nuxt: Watch server/ for builder:watch hook (#โ€‹34208)
  • nitro: Preserve error.message for fatal errors (#โ€‹34226)
  • Only enable dynamic imports when ts plugin (#โ€‹34205)
  • webpack: Use H3Error for 403 in dev server (#โ€‹34233)
  • nuxt: Ensure NuxtError extends Error type (#โ€‹34242)
  • vite: Use H3Error for 404 in dev server (#โ€‹34225)
  • nuxt: Add backwards compat for #app barrel export in keyed functions (#โ€‹34199)
  • nuxt: Track + re-add custom routes on hmr (#โ€‹32044)
  • nuxt: Keep vnode when leaving deeper nested route (#โ€‹33778)
  • vite: Prevent CSS flickering in dev mode after config changes (#โ€‹33856)
  • nuxt: Do not start view transition if there is no route (#โ€‹33723)
  • nuxt: Call deferHydration done on NuxtPage unmount (#โ€‹34152)
  • nuxt: Handle invalid datetime in ` (#โ€‹33992)
  • nuxt: Preserve middleware error status in 404 fallback (#โ€‹34148)
  • nitro: Do not augment nuxt/schema (#โ€‹34255)
  • nuxt: Cache manifest files to preserve buildId (#โ€‹34002)
  • nuxt: Don't decode query string in SSR context URL (#โ€‹34252)
  • nuxt: Allow specifying moduleDependencies by meta.name (#โ€‹34263)
  • nuxt: Resolve #components import mapping conflict for packages outside rootDir (#โ€‹34139)
  • vite,webpack: Use node.res to send 403/404 (#โ€‹34266)
  • nitro,nuxt: Align path encoding with vue-router (#โ€‹34265)
  • nitro: Augment nuxt/schema once more (552bbd8d1)
๐Ÿ’… Refactors
  • nuxt: Prefer genObjectKey to omit unnecessary quotes (#โ€‹34245)
  • nuxt: Use ComponentProps helper to extract layout props (#โ€‹34248)
๐Ÿ“– Documentation
๐Ÿก Chore
โœ… Tests
  • Vitest v4 compatibility (825b2c202)
  • Add runtime tests for deeply nested <NuxtPage> navigation (048efc030)
โค๏ธ Contributors

v4.3.0

Compare Source

4.3.0 is the next minor release.

Nuxt 4.3 brings powerful new features for layouts, caching, and developer experience โ€“ plus significant performance improvements under the hood.

๐Ÿ“ฃ Some News

Extended v3 Support

Early this month, I opened a discussion to find out how the upgrade had gone from v3 to v4. I was really pleased to hear how well it had gone for most people.

Having said that, we're committed to making sure no one gets left behind. And so we will continue to provide security updates and critical bug fix releases beyond the previously announced end-of-life date of January 31, 2026, meaning Nuxt v3 will meet its end-of-life on July 31, 2026.

[!TIP]
As usual, today also brings a minor release for v3, with many of the same improvements backported from v4.3.

Preparing for Nuxt 5

We're closer than ever to the releases of Nuxt v5 and Nitro v3. In the coming weeks, the main branch of the Nuxt repository will begin receiving initial commits for Nuxt 5. However, it's still business as usual.

  • Continue making pull requests to the main branch
  • We'll backport changes to the 4.x and 3.x branches

Keep an eye out on the Upgrade Guide โ€“ we'll be adding details about how you can already start migrating your projects to prepare for Nuxt v4 with future.compatibilityVersion: 5.

๐Ÿ—‚๏ธ Route Rule Layouts

But that's enough about the future. We have a lot of good things for you today!

First, you can now set layouts directly in route rules using the new appLayout property (#โ€‹31092). This provides a centralized, declarative way to manage layouts across your application without scattering definePageMeta calls throughout your pages.

export default defineNuxtConfig({
  routeRules: {
    '/admin/**': { appLayout: 'admin' },
    '/dashboard/**': { appLayout: 'dashboard' },
    '/auth/**': { appLayout: 'minimal' }
  }
})

This might be useful for:

  • Admin panels with a shared layout across many routes
  • Marketing pages that need a different layout from the app

[!TIP]
Plus, you can pass props to layouts now! See the setPageLayout improvements below.

๐Ÿ“ฆ ISR/SWR Payload Extraction

Payload extraction now works with ISR (incremental static regeneration), SWR (stale-while-revalidate) and cache routeRules (#โ€‹33467). Previously, only pre-rendered pages could generate _payload.json files.

This means:

  • Client-side navigation to ISR/SWR pages can use cached payloads
  • CDNs (Vercel, Netlify, Cloudflare) can cache payload files alongside HTML
  • Fewer API calls during navigation โ€“ data can be prefetched and served from the cached payload
export default defineNuxtConfig({
  routeRules: {
    '/products/**': { 
      isr: 3600, // Revalidate every hour
    }
  }
})

๐Ÿงน Dev Mode Payload Extraction

Related to the above, payload extraction now also works in development mode (#โ€‹30784). This makes it easier to test and debug payload behavior without needing to run a production build.

[!IMPORTANT]
Payload extraction works in dev mode with nitro.static set to true, or for individual pages which have isr, swr, prerender or cache route rules.

๐Ÿšซ Disable Modules from Layers

When extending Nuxt layers, you can now disable specific modules that you don't need (#โ€‹33883). Just pass false to the module's options:

export default defineNuxtConfig({
  extends: ['../shared-layer'],
  // disable @&#8203;nuxt/image from layer
  image: false,
})

๐Ÿท๏ธ Route Groups in Page Meta

Route groups (folders wrapped in parentheses like (protected)/) are now exposed in page meta (#โ€‹33460). This makes it easy to check which groups a route belongs to in middleware or anywhere you have access to the route.

<script setup lang="ts">
// This page's meta will include: { groups: ['protected'] }
useRoute().meta.groups
</script>
export default defineNuxtRouteMiddleware((to) => {
  if (to.meta.groups?.includes('protected') && !isAuthenticated()) {
    return navigateTo('/login')
  }
})

This provides a clean, convention-based approach to route-level authorization without needing to add definePageMeta to every protected page.

๐ŸŽจ Layout Props with setPageLayout

The setPageLayout composable now accepts a second parameter to pass props to your layout (#โ€‹33805):

export default defineNuxtRouteMiddleware((to) => {
  setPageLayout('admin', {
    sidebar: true,
    theme: 'dark'
  })
})
<script setup lang="ts">
defineProps<{
  sidebar?: boolean
  theme?: 'light' | 'dark'
}>()
</script>

๐Ÿ”ง #server Alias

A new #server alias provides clean imports within your server directory (#โ€‹33870), similar to how #shared works:

// Before: relative path hell
import { helper } from '../../../../utils/helper'

// After: clean and predictable
import { helper } from '#server/utils/helper'

The alias includes import protection โ€“ you can't accidentally import #server code from client or shared contexts.

๐ŸชŸ Draggable Error Overlay

The development error overlay introduced in Nuxt 4.2 is now draggable and can be minimized (#โ€‹33695). You can:

  • Drag it to any corner of the screen (it snaps to edges)
  • Minimize it to a small pill button when you want to keep working
  • Your position and minimized state persist across page reloads

This is a quality-of-life improvement when you're iterating on fixes and don't want the overlay blocking your view.

https://github.com/user-attachments/assets/nuxt_4-3_error_demo.mp4

โš™๏ธ Async Plugin Constructors

Module authors can now use async functions when adding build plugins (#โ€‹33619):

export default defineNuxtModule({
  async setup() {
    // Lazy load only when actually needed
    addVitePlugin(() => import('my-cool-plugin').then(r => r.default()))
    
    // No need to load webpack plugin if using Vite
    addWebpackPlugin(() => import('my-cool-plugin/webpack').then(r => r.default()))
  }
})

This enables true lazy loading of build plugins, avoiding unnecessary code loading when plugins aren't needed.

๐Ÿš€ Performance Improvements

This release includes several performance optimizations for faster builds:

  • Hook filters - Internal plugins now use filters to avoid running hooks unnecessarily (#โ€‹33898)
  • SSR styles optimization - The nuxt:ssr-styles plugin is now significantly faster (#โ€‹33862, #โ€‹33865)
  • Layer alias transform - Skipped when using Vite (it handles this natively) (#โ€‹33864)
  • Route rules compilation - Route rules are now compiled into a client chunk using rou3, removing the need for radix3 in the client bundle and eliminating app manifest fetches (#โ€‹33920)

๐ŸŽจ Inline Styles for Webpack/Rspack

The inlineStyles feature now works with webpack and rspack builders (#โ€‹33966), not just Vite. This enables critical CSS inlining for better Core Web Vitals regardless of your bundler choice.

โš ๏ธ Deprecations

statusCode โ†’ status, statusMessage โ†’ statusText

In preparation for Nitro v3 and H3 v2, we're moving to use Web API naming conventions (#โ€‹33912). The old properties still work but are deprecated in advance of v5:

- throw createError({ statusCode: 404, statusMessage: 'Not Found' })
+ throw createError({ status: 404, statusText: 'Not Found' })

๐Ÿ› Bug Fixes

Notable fixes in this release:

  • Fixed head component deduplication using key attribute (#โ€‹33958, #โ€‹33963)
  • Fixed async data properties not being reactive in Options API (#โ€‹34119)
  • Fixed useCookie unsafe number parsing during decode (#โ€‹34007)
  • Fixed NuxtPage not re-rendering when nested NuxtLayout has layouts disabled (#โ€‹34078)
  • Fixed client-side pathname decoding for non-ASCII route aliases (#โ€‹34043)
  • Fixed suspense remounting when navigating after pending state (#โ€‹33991)
  • Fixed clipboard copy in error overlay (#โ€‹33873)
  • Enabled allowArbitraryExtensions by default in TypeScript config (#โ€‹34084)
  • Added noUncheckedIndexedAccess to server tsconfig for safer typing (#โ€‹33985)

[!IMPORTANT]
Enabling noUncheckedIndexedAccess in the Nitro server TypeScript config improves type safety but may surface new type errors in your server code. This change was necessary because Nuxt's app context performs type checks on server routes (learn more).

While we recommend keeping this enabled for better type safety, you can disable it if needed:

export default defineNuxtConfig({
  nitro: {
    typescript: {
      tsConfig: {
        compilerOptions: {
          noUncheckedIndexedAccess: false
        }
      }
    }
  }
})

Note that disabling this may allow type errors to slip through that could cause runtime issues with indexed access.

๐Ÿ“š Documentation

๐ŸŽ‰ Nuxt 3.21.0

Alongside v4.3.0, we're releasing Nuxt v3.21.0 with many of the same improvements backported to the 3.x branch. This release includes:

  • All the same features: Route rule layouts, ISR payload extraction, layout props with setPageLayout, #server alias, draggable error overlay, and more
  • All performance improvements: SSR styles optimization, hook filters, and route rules compilation
  • Module disabling: Disable layer modules by setting options to false
  • Critical bug fixes: Async data reactivity in Options API, useCookie number parsing, head component deduplication, and more

โœ… Upgrading

Our recommendation for upgrading is to run:

npx nuxt upgrade --dedupe

# or, if you are upgrading to v3.21
npx nuxt@latest upgrade --dedupe --channel=v3

This will deduplicate your lockfile and help ensure you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

[!TIP]
Check out our upgrade guide if upgrading from an older version.

๐Ÿ‘‰ Changelog

compare changes

๐Ÿš€ Enhancements
๐Ÿ”ฅ Performance
  • nuxt: Do not init layer alias transform when using vite (#โ€‹33864)
  • vite: Add hook filters for ssr styles plugin (#โ€‹33865)
  • vite: Optimize nuxt:ssr-styles plugin (#โ€‹33862)
  • nuxt: Use filter for vfs plugin load (eb3d2d4c6)
  • nuxt,vite: Use filters to avoid running hooks unnecessarily (6b7fc7477)
  • nuxt,vite: Add more filters to internal plugins (#โ€‹33898)
๐Ÿฉน Fixes
  • kit: Normalize local layer paths with trailing slashes (#โ€‹33858)
  • nuxt: Avoid overwriting multiple head input in island handler (#โ€‹33849)
  • nuxt: Update meta instead of calling router.replace in page hmr (#โ€‹33897)
  • nuxt: Don't call page:loading:end in cache if already called (7789f73bd)
  • vite: Add error handling for parsing NUXT_VITE_NODE_OPTIONS (41a564d23)
  • nuxt: Do not skip middleware when appMiddleware references invalid key (323f27bc8)
  • nitro: Clipboard copy in error overlay (#โ€‹33873)
  • webpack,rspack: Resolve deep imports in virtual files (#โ€‹33927)
  • webpack: Disable async chunks in dev mode (0310c4070)
  • webpack: Correctly evaluate sourcemap name (653f364af)
  • nuxt: Handle node10 resolution for nuxt/meta (01c2c9b13)
  • nuxt: Do not early return if component priorities conflict (#โ€‹33955)
  • nuxt: Use key for tag deduplication in <Head> component (#โ€‹33958)
  • schema,vite: Resolve build.transpile when initialising vite (#โ€‹33868)
  • nuxt,rspack,webpack: Inject module identifiers for webpack builders (#โ€‹33962)
  • nuxt: Add key to head components for proper deduplication (#โ€‹33963)
  • nitro: Check prettyResponse.body type before error overlay (#โ€‹33977)
  • nuxt: Don't URI-encode static route paths (#โ€‹33990)
  • nuxt: Skip internal stub routes from prerender (#โ€‹34001)
  • kit,schema: Align module onUpgrade arguments with types (#โ€‹33988)
  • nuxt: Handle unsafe number parsing in useCookie decode (#โ€‹34007)
  • nuxt: Do not externalise rou3 (2df4e1ae3)
  • nitro: Add noUncheckedIndexedAccess to server tsconfig (#โ€‹33985)
  • nuxt: Add auto-import declarations for shared/ context (#โ€‹33978)
  • nuxt: Update global reference to globalThis in useRequestFetch (#โ€‹33976)
  • vite: Configure hmr port for server build (#โ€‹33929)
  • kit: Add forward compatible nitro v3 types (#โ€‹34053)
  • nitro,nuxt: Do not import nitro deps in builders (#โ€‹34054)
  • nitro: Add h3 types to auto-imports (#โ€‹34035)
  • schema: Add some more directories to ignore (ebc2a66ab)
  • nitro: Also augment nuxt/schema (a6a044d81)
  • nuxt: Make asyncData properties reactive in Options API (#โ€‹34119)
  • nuxt: Rerender NuxtPage when nested NuxtLayout has explicitly disabled layouts (#โ€‹34078)
  • kit,nitro: Enable allowArbitraryExtensions by default (#โ€‹34084)
  • nuxt: Decode client-side pathname for non-ASCII route aliases (#โ€‹34043)
  • nuxt: Force remount suspense when navigating after pending (#โ€‹33991)
  • nuxt: Add documentation link to server builder error message (#โ€‹34122)
  • nuxt: Validate placeholder/fallback tags + warn about placeholder/fallback props (567a1c6fb)
  • nuxt: Force flush useAsyncData debounced execute post watcher flush (#โ€‹34125)
  • nitro: Process isr/swr/cache keys (d84278622)
  • nuxt: Add typeFrom support for imports.d.ts template exports (#โ€‹34135)
  • nuxt: Ensure we inline styles for hydrate-never components (#โ€‹34132)
๐Ÿ’… Refactors
  • kit: Add explicit return types for kit utilities (6cd1289d1)
  • nitro,nuxt,schema,vite: Provide explicit return types (1d2c0c25f)
  • kit,nuxt,schema: Use named imports from defu + consola (322dae3e0)
  • Add explicit .ts file extensions to relative imports (80778c0cd)
  • kit,nitro,nuxt,schema: Reduce barrels + move <> to as (f1713850c)
  • nitro,nuxt: Use ~ prefix for internal ssrContext properties (#โ€‹33896)
  • nitro: Add explicit return types for runtime utils (a4fda917e)
  • nitro: Move tree-shaken flags from replace plugin -> vfs (#โ€‹33907)
  • nitro,nuxt,vite,webpack: Use status/statusText + deprecate old props (#โ€‹33912)
  • webpack: Use RuntimeModule API for chunk preloads (#โ€‹33930)
  • nuxt: Use AST-aware function key injection (#โ€‹33446)
  • nitro,nuxt,schema: Use augments for nitro schema types (#โ€‹34039)
  • nitro,rspack,vite,webpack: Move cors handling -> nitro builder (#โ€‹34048)
๐Ÿ“– Documentation
๐Ÿ“ฆ Build
  • Remove babel debugging plugin from jiti stub options (bce8248b4)
  • vite: Add build entries for vite-node entrypoints (#โ€‹33893)
  • nuxt: Tidy up subpath export types (a63d4a014)
  • Use obuild except for nuxt + nitro-server packages (#โ€‹34049)
  • schema: Fix /builder-env subpath types (7f5034288)
๐Ÿก Chore
โœ… Tests
๐Ÿค– CI
โค๏ธ Contributors

v4.2.2

Compare Source

4.2.2 is the next patch release.

โœ… Upgrading

Our recommendation for upgrading is to run:

npx nuxt 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

compare changes

๐Ÿฉน Fixes
  • nitro: Do not show pretty error handler when testing (243261edb)
  • nuxt: Generate valid references for component declaration items (#โ€‹33388)
  • nuxt: Sync internal route before calling page:finish hook (#โ€‹33707)
  • kit: Add TypeScript path alias support for test files (#โ€‹33672)
  • nitro: Ensure html is a string before injecting error handler (f70b70c97)
  • nitro: Include layer server directories in tsconfig.server.json (#โ€‹33510)
  • nuxt: Ensure deduped async data executions return latest promise (#โ€‹33740)
  • kit,nuxt: Type + respect moduleDependencies by meta name (#โ€‹33774)
  • nuxt,schema: Ignore .d.vue.ts declarations (1c73525a2)
  • kit,nuxt: Protect against resolved nuxt module subpath (#โ€‹33767)
  • nuxt: Re-execute callOnce during HMR (#โ€‹33810)
  • nuxt: Resolve watch callback after reactive key change in useAsyncData (#โ€‹33802)
  • nuxt: Escape HTML in development error page stack trace (#โ€‹33820)
  • kit: Do not add resolved rootDir to cached layer config (#โ€‹33779)
  • kit,schema: Add moduleDependencies -> installModule (#โ€‹33689)
๐Ÿ’… Refactors
  • nuxt: Improve type safety within callOnce function (#โ€‹33825)
๐Ÿ“– Documentation
๐Ÿก Chore
  • Update pnpm to 10.21 and enable trust policy (d2c9711c0)
  • Revert pnpm trust policy and restore provenance action (f9d0e0a3d)
  • Update markdownlint config to ignore mdc issues (e7fff7132)
  • Pin to single version of unstorage (ec316eae8)
โœ… Tests
  • Add patchProp and nodeOps to excluded Vue helpers (#โ€‹33754)
  • Use fake timers for watch params test (08d9d2f3b)
๐Ÿค– CI
โค๏ธ Contributors

v4.2.1

Compare Source

4.2.1 is the next patch release.

โœ… Upgrading

Our recommendation for upgrading is to run:

npx nuxt 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

compare changes

๐Ÿฉน Fixes
  • kit,nuxt,schema: Deprecate ImportPresetWithDeprecation (#โ€‹33596)
  • nuxt: Correct warning message for prefetch/noPrefetch conflict (#โ€‹33617)
  • nitro: Remove <nuxt-error-overlay> iframe border (#โ€‹33625)
  • vite: Use rolldown replace only in build (#โ€‹33615)
  • nitro: Use directory paths in moduleEntryPaths (#โ€‹33628)
  • nitro: Start error overlay minimized based on status code (#โ€‹33658)
  • vite: Ensure optimizeDeps config is applied before other plugins (#โ€‹33586)
  • nuxt: Respect layer priority order for scanned components (#โ€‹33654)
  • nuxt: Process prerender routes on pages:resolved (#โ€‹33662)
  • nuxt: Remove abort signal event listeners after render (#โ€‹33665)
  • nuxt: Cleanup event listener with cleanup signal (#โ€‹33667)
  • vite: Update vite-node (#โ€‹33663)
  • vite: Respect vite proxy in dev middleware (#โ€‹33670)
๐Ÿ’… Refactors
  • kit,nitro,nuxt,schema,vite: Explicitly import process/performance (#โ€‹33650)
๐Ÿ“– Documentation
๐Ÿก Chore
๐Ÿค– CI
  • Disable cache in release action (ff37598bc)
โค๏ธ Contributors

v4.2.0

Compare Source

4.2.0 is the next minor release.

๐Ÿ‘€ Highlights

We're excited to announce Nuxt 4.2, bringing new capabilities for better TypeScript DX, enhanced error handling, and improved control over data fetching! ๐ŸŽ‰

๐ŸŽฏ Abort Control for Data Fetching

You can now use AbortController signals directly within useAsyncData, giving you fine-grained control over request cancellation (#โ€‹32531).

This works by passing an internal signal to your useAsyncData handler to cancel any promise that can be canceled, such as $fetch.

<script setup lang="ts">
const controller = new AbortController()

const { data, error, clear, refresh } = await useAsyncData('users', (_nuxtApp, { signal }) => $fetch('/api/users', {
  signal
}))

refresh() // will actually cancel the $fetch request (if dedupe: cancel)
refresh() // will actually cancel the $fetch request (if dedupe: cancel)
refresh()
  
clear() // will cancel the latest pending handler
</script>

You also pass an AbortController signal directly to refresh/execute, giving you fine-grained control over request cancellation. This is particularly useful when you need to abort requests based on user actions or component lifecycle events.

const { data, refresh } = await useAsyncData('posts', fetchPosts)

// Abort an ongoing refresh
const abortController = new AbortController()
refresh({ signal: abortController.signal })

// Later...
abortController.abort()
๐ŸŽจ Better Error Pages in Development

When an error occurs during development, Nuxt will now display both your custom error page and a detailed technical error overlay (#โ€‹33359). This gives you the best of both worlds โ€“ you can see what your users will experience while also having immediate access to stack traces and debugging information.

Screenshot of the new development error page

The technical overlay appears as a toggleable panel that doesn't interfere with your custom error page, making it easier to debug issues while maintaining a realistic preview of your error handling.

๐Ÿ”ฎ Opt-in Vite Environment API

For those wanting to experiment with cutting-edge features, you can now opt into the Vite Environment API (#โ€‹33492).

The Vite Environment API is a major architectural improvement in Vite 6. It closes the gap between development and production by allowing the Vite dev server to handle multiple environments concurrently (rather than requiring multiple Vite dev servers, as we have done previously in Nuxt).

This should improve performance when developing and eliminate some edge case bugs.

... and it is the foundation for implementing Nitro as a Vite environment, which should speed up the dev server still further, as well as allowing more greater alignment in development with your Nitro preset.

export default defineNuxtConfig({
  experimental: {
    viteEnvironmentApi: true
  }
})

This is also the first breaking change for Nuxt v5. You can opt in to these breaking changes by setting compatibilityVersion to 5:

export default defineNuxtConfig({
  future: {
    compatibilityVersion: 5
  },
})

Please only use this for testing, as this opts in to unlimited future breaking changes, including updating to Nitro v3 once we ship the Nuxt integration.

[!WARNING]
This is highly experimental and the API may change. Only enable if you're prepared for potential breaking changes and want to help shape the future of Nuxt!

๐Ÿ“ฆ New @nuxt/nitro-server Package

We've extracted Nitro server integration into its own package: @nuxt/nitro-server ([#โ€‹33462](https://redirect.github.com/nuxt/nuxt/pu

โœ‚ Note

PR body was truncated to here.

Configuration

๐Ÿ“… Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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.

@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 24, 2026 •
edited
Loading

โŒ Deploy Preview for ts-maps failed. Why did it fail? โ†’

Name Link
๐Ÿ”จ Latest commit 2e902d7
๐Ÿ” Latest deploy log https://app.netlify.com/projects/ts-maps/deploys/69f3a11a15c3360008c22925

@renovate renovate Bot force-pushed the renovate/major-nuxtjs-monorepo branch 2 times, most recently from 3917f6d to d731d5f Compare April 30, 2026 00:37
@renovate renovate Bot force-pushed the renovate/major-nuxtjs-monorepo branch from d731d5f to 2e902d7 Compare April 30, 2026 18:36
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

dependencies major

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants