chore(deps): update all non-major dependencies

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
@happy-dom/global-registrator (source)	^20.0.10 → ^20.5.0					devDependencies	minor
@nuxt/devtools (source)	^3.1.0 → ^3.1.1					devDependencies	patch
@nuxt/eslint-config (source)	^1.10.0 → ^1.14.0					devDependencies	minor
@nuxt/kit (source)	^4.2.1 → ^4.3.0					dependencies	minor
@nuxt/schema (source)	^4.2.1 → ^4.3.0					devDependencies	minor
@stacksjs/stx	>=0.1.0 → >=0.2.0					peerDependencies	minor
@tailwindcss/postcss (source)	^4.1.17 → ^4.1.18					devDependencies	patch
@types/bun (source)	^1.3.2 → ^1.3.8					devDependencies	patch
@types/node (source)	^24.10.0 → ^24.10.11					devDependencies	patch
@types/react (source)	^19.2.2 → ^19.2.13					devDependencies	patch
@types/react-dom (source)	^19.2.2 → ^19.2.3					devDependencies	patch
@vitejs/plugin-react (source)	^5.1.0 → ^5.1.3					dependencies	patch
@vitejs/plugin-vue (source)	^6.0.1 → ^6.0.4					devDependencies	patch
@vitejs/plugin-vue (source)	^6.0.1 → ^6.0.4					dependencies	patch
actions/checkout	v5.0.0 → v5.0.1					action	patch
better-dx	^0.2.3 → ^0.2.5					dependencies	patch
bumpp	^10.3.1 → ^10.4.1					devDependencies	minor
bun-types (source)	^1.3.2 → ^1.3.8					dependencies	patch
bun-types (source)	^1.3.2 → ^1.3.8					devDependencies	patch
eslint (source)	^9.39.1 → ^9.39.2					devDependencies	patch
eslint-config-next (source)	16.0.1 → 16.1.6					devDependencies	minor
happy-dom	^20.0.10 → ^20.5.0					devDependencies	minor
lint-staged	^16.2.6 → ^16.2.7					devDependencies	patch
node	24.11.0 → 24.13.0					uses-with	minor
nuxt (source)	^4.2.1 → ^4.3.0					dependencies	minor
nuxt (source)	^4.2.1 → ^4.3.0					devDependencies	minor
oven-sh/setup-bun	v2.0.2 → v2.1.2					action	minor
react (source)	19.2.0 → 19.2.4					dependencies	patch
react (source)	^19.2.0 → ^19.2.4					peerDependencies	patch
react (source)	^19.2.0 → ^19.2.4					devDependencies	patch
react-dom (source)	19.2.0 → 19.2.4					dependencies	patch
react-dom (source)	^19.2.0 → ^19.2.4					peerDependencies	patch
react-dom (source)	^19.2.0 → ^19.2.4					devDependencies	patch
shivammathur/setup-php	2.35.5 → 2.36.0					action	minor
tailwindcss (source)	^4.1.17 → ^4.1.18					devDependencies	patch
vite (source)	^7.2.2 → ^7.3.1					devDependencies	minor
vite (source)	^7.2.2 → ^7.3.1					dependencies	minor
vue (source)	^3.5.24 → ^3.5.27					dependencies	patch
vue (source)	^3.5.24 → ^3.5.27					devDependencies	patch
vue-router (source)	4.6.3 → 4.6.4					dependencies	patch
vue-tsc (source)	^3.1.3 → ^3.2.4					devDependencies	minor

---

Release Notes

capricorn86/happy-dom (@​happy-dom/global-registrator)

v20.5.0

Compare Source

v20.4.0

Compare Source

🎨 Features

• Adds support for caching the compiled code of EcmaScript modules - By @​capricorn86 in task #​2049
• Improves the way nodes are destroyed and garbage collected - By @​capricorn86 in task #​2049

v20.3.9

Compare Source

👷‍♂️ Patch fixes

• Accept Document nodes as valid boundary points in Selection API - By @​skoch13 in task #​1952

v20.3.8

Compare Source

👷‍♂️ Patch fixes

• The getters for the properties focusNode and focusOffset in the Selection API returned incorrect values - By @​skoch13 in task #​1850

v20.3.7

Compare Source

👷‍♂️ Patch fixes

• Updates README.md for the "@​happy-dom/server-renderer" package - By @​capricorn86 in task #​2035

v20.3.6

Compare Source

👷‍♂️ Patch fixes

• Fixes issue where it wasn't possible to toggle the "open" attribute of <details> by clicking on a child of the <summary> element - By @​Nxooah in task #​1928

v20.3.5

Compare Source

👷‍♂️ Patch fixes

• Use internal property for "location" in BrowserFrameURL to avoid mock interference - By @​marchaos in task #​1964
• Add optional chaining to the "hostname" and pathname" properties to check if they are undefined in CookieURLUtility - By @​marchaos in task #​1968

v20.3.4

Compare Source

v20.3.3

Compare Source

v20.3.2

Compare Source

v20.3.1

Compare Source

👷‍♂️ Patch fixes

• Normalizes the "format" parameter according to the HTML specification in DataTransfer.getData() - By @​marchaos in task #​1965
• Handle partial responses in XMLHttpRequest - By @​rexxars in task #​1890

v20.3.0

Compare Source

🎨 Features

• Use RegExp to convert ASCII character casing to improve performance - By @​TrevorBurnham in task #​1886

v20.2.0

Compare Source

🎨 Features

• Use Element.classList.contains() instead of splitting className in query selectors to improve performance as it's cached - By @​TrevorBurnham in task #​1884

v20.1.1

Compare Source

👷‍♂️ Patch fixes

• Fixes caching in querySelector() - By @​TrevorBurnham in task #​1882
• Avoid sort in querySelector() to improve performance - By @​TrevorBurnham in task #​1882

v20.1.0

Compare Source

🎨 Features

• Adds support for BrowserPage.evaluateModule() and BrowserFrame.evaluateModule() - By @​capricorn86 in task #​1944
• Adds support for module to the browser settings - By @​capricorn86 in task #​1944
  • This makes it possible to add a custom resolver or a node module resolver
• Adds support for dynamic import() to JavaScript evaluation - By @​capricorn86 in task #​1944
  • It was previously only supported when using type="module" on script elements
• Adds support for WebSocket - By @​capricorn86 in task #​1944
• Adds support for CloseEvent - By @​capricorn86 in task #​1944
• Adds support for render.setupScript and render.mode to the configuration in @​happy-dom/server-renderer - By @​capricorn86 in task #​1944
• Changes name from urls to renderItems in the configuration in @​happy-dom/server-renderer - By @​capricorn86 in task #​1944
• Adds support for rendering strings in @​happy-dom/server-renderer - By @​capricorn86 in task #​1944
• Makes JavaScript evaluation disabled by default in @​happy-dom/server-renderer - By @​capricorn86 in task #​1944

👷‍♂️ Patch fixes

• Several fixed to the EcmaScript module compiler (esm) - By @​capricorn86 in task #​1944
• Fixes issue where rendering using Worker's didn't work in @​happy-dom/server-renderer - By @​capricorn86 in task #​1944

v20.0.11

Compare Source

nuxt/devtools (@​nuxt/devtools)

v3.1.1

Compare Source

Bug Fixes

• ui: remove flash when switching to dark (#​909) (75a814f)

Features

• support passing additional permissions to the iframe (#​911) (bc1d11c)

nuxt/eslint (@​nuxt/eslint-config)

v1.14.0

Compare Source

   🚀 Features

• eslint-config: Add no-page-meta-runtime-values  -  by @​danielroe in #​641 (b74a0)

    View changes on GitHub

v1.13.0

Compare Source

   🚀 Features

• Upgrade eslint-flat-config-utils eslint-plugin-import-lite and eslint-plugin-jsdoc  -  by @​antfu (10bf9)

    View changes on GitHub

v1.12.1

Compare Source

No significant changes

    View changes on GitHub

v1.11.0

Compare Source

   🚀 Features

• Allow config key sorting on files not named nuxt.config  -  by @​benedictleejh in #​630 (be2e9)

    View changes on GitHub

nuxt/nuxt (@​nuxt/kit)

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 @​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

• Improved module author guides with clearer structure (#​33803)
• Added MCP setup instructions for Claude Desktop (#​33914)
• Added layers directory documentation (#​33967)
• Added Deno package manager examples (#​34070)
• Clarified type-checking context limitations for server routes (#​33964)

🎉 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

• kit: Support async constructor for adding plugins (#​33619)
• kit: Export Nuxt major version type (#​33700)
• schema: Add #server alias for server directory imports (#​33870)
• ui-templates: Let it snow! ❄️ (#​33804)
• schema: Hoist nitro crossws types (5b16a51f5)
• nitro,nuxt: Compile route rules into client chunk (#​33920)
• nuxt: Allow disabling modules by setting module options to false (#​33883)
• kit: Allow specifying moduleDependencies as an async function (#​33504)
• nuxt: Support appLayout in route rules (#​31092)
• nuxt: Add route groups to page meta (#​33460)
• nuxt: Enable payload extraction for ISR/SWR routes (#​33467)
• nuxt: Allow updating props with setPageLayout (#​33805)
• nuxt: Enable dragging and minimizing for error overlay (#​33695)
• nitro,nuxt: Add support for payload extraction in dev (#​30784)
• rspack,webpack: Add inline styles (#​33966)
• kit: Add forward-compatible nitro types (#​34036)

🔥 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,webpa

---

Configuration

📅 Schedule: 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[netlify]

❌ Deploy Preview for ts-maps failed. Why did it fail? →

Name	Link
🔨 Latest commit	35a4b2b
🔍 Latest deploy log	https://app.netlify.com/projects/ts-maps/deploys/6987129534a2ca000852fd63

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/stacksjs/ts-maps@483

commit: 3fdb3a3