Skip to content

fix(deps): update root #42

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update root #42

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 1, 2025 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@antfu/eslint-config 2.10.0 → 2.27.3 age confidence
@nuxt/kit (source) ^3.11.1 → ^3.21.0 age confidence
@nuxt/module-builder ^0.5.5 → ^0.8.4 age confidence
@nuxt/schema (source) ^3.11.1 → ^3.21.0 age confidence
@nuxt/test-utils ^3.12.0 → ^3.23.0 age confidence
@types/node (source) ^20.11.30 → ^20.19.30 age confidence
@vitejs/plugin-vue (source) ^5.0.4 → ^5.2.4 age confidence
@vitest/coverage-v8 (source) ^1.4.0 → ^1.6.1 age confidence
bumpp ^9.4.0 → ^9.11.1 age confidence
lint-staged ^15.2.2 → ^15.5.2 age confidence
playwright-core (source) ^1.42.1 → ^1.58.1 age confidence
simple-git-hooks ^2.11.1 → ^2.13.1 age confidence
typescript (source) ^5.4.3 → ^5.9.3 age confidence
unconfig (source) ^0.3.11 → ^0.6.1 age confidence
unplugin-vue-macros (source) ^2.7.13 → ^2.14.5 age confidence
vue (source) ^3.4.21 → ^3.5.27 age confidence

Release Notes

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

v2.27.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.27.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.27.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.27.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.26.1

Compare Source

No significant changes

    View changes on GitHub

v2.26.0

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.25.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.25.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.25.0

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.24.1

Compare Source

   🚀 Features
    View changes on GitHub

v2.24.0

Compare Source

   🚀 Features
    View changes on GitHub

v2.23.2

Compare Source

No significant changes

    View changes on GitHub

v2.23.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.23.0

Compare Source

   🚀 Features
  • Introduce type options, enable ts/explicit-function-return-type for lib  -  by @​antfu (3dd7b)
   🐞 Bug Fixes
    View changes on GitHub

v2.22.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.22.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.22.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.22.1

Compare Source

No significant changes

    View changes on GitHub

v2.22.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.21.3

Compare Source

No significant changes

    View changes on GitHub

v2.21.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.21.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.21.0

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.20.0

Compare Source

   🚀 Features
    View changes on GitHub

v2.19.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.19.1

Compare Source

   🚀 Features
    View changes on GitHub

v2.19.0

Compare Source

   🚀 Features
    View changes on GitHub

v2.18.1

Compare Source

   🚀 Features
    View changes on GitHub

v2.18.0

Compare Source

   🚀 Features
    View changes on GitHub

v2.17.0

Compare Source

   🚀 Features
    View changes on GitHub

v2.16.4

Compare Source

No significant changes

    View changes on GitHub

v2.16.3

Compare Source

   🚀 Features
    View changes on GitHub

v2.16.2

Compare Source

No significant changes

    View changes on GitHub

v2.16.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.16.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.15.0

Compare Source

   🚨 Breaking Changes
    View changes on GitHub

v2.14.0

Compare Source

   🚀 Features
    View changes on GitHub

v2.13.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.13.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.13.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.13.1

Compare Source

   🚀 Features
    View changes on GitHub

v2.13.0

Compare Source

   🚀 Features
    View changes on GitHub

v2.12.2

Compare Source

   🚀 Features
    View changes on GitHub

v2.12.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.12.0

Compare Source

   🚀 Features
    View changes on GitHub

v2.11.6

Compare Source

   🚀 Features
    View changes on GitHub

v2.11.5

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.11.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.11.3

Compare Source

   🚀 Features
    View changes on GitHub

v2.11.2

Compare Source

No significant changes

    View changes on GitHub

v2.11.1

Compare Source

   🚀 Features
    View changes on GitHub

v2.11.0

Compare Source

   🚀 Features
    View changes on GitHub

v2.10.1

Compare Source

No significant changes

    View changes on GitHub
nuxt/nuxt (@​nuxt/kit)

v3.21.0

Compare Source

3.21.0 is the next minor release.

Nuxt 4.3 and 3.21 bring 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@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)
  • schema: Hoist nitro crossws types (6ff79ea6c)
  • 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

Configuration

📅 Schedule: Branch creation - "every 8 months on the first day of the month" (UTC), 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.

@renovate renovate bot added the dependencies label Jan 1, 2025
@renovate renovate bot force-pushed the renovate/root branch 4 times, most recently from 6cf4f5d to 0f2f8d9 Compare January 6, 2025 11:18
@renovate renovate bot force-pushed the renovate/root branch 8 times, most recently from 038f3f0 to f66baad Compare January 15, 2025 06:56
@renovate renovate bot force-pushed the renovate/root branch 9 times, most recently from 8db8172 to 52fb833 Compare January 22, 2025 11:40
@renovate renovate bot force-pushed the renovate/root branch 8 times, most recently from d1792a7 to 88bcb57 Compare January 29, 2025 11:25
@renovate renovate bot force-pushed the renovate/root branch 5 times, most recently from 6a8bbc4 to a00adcd Compare November 12, 2025 05:49
@renovate renovate bot force-pushed the renovate/root branch 3 times, most recently from c073955 to 98a6b60 Compare November 25, 2025 12:57
@renovate renovate bot force-pushed the renovate/root branch 4 times, most recently from 719ce71 to 26d4b12 Compare December 9, 2025 17:41
@renovate renovate bot force-pushed the renovate/root branch 2 times, most recently from 5559790 to 187b221 Compare December 18, 2025 15:43
@renovate renovate bot force-pushed the renovate/root branch 3 times, most recently from 2512766 to 219d2da Compare January 6, 2026 19:02
@renovate renovate bot force-pushed the renovate/root branch 4 times, most recently from 209bb2d to 7af4a69 Compare January 15, 2026 19:10
@renovate renovate bot force-pushed the renovate/root branch 5 times, most recently from 14fd50e to cdb5638 Compare January 23, 2026 20:51
@renovate renovate bot force-pushed the renovate/root branch 2 times, most recently from b119899 to 0f021dc Compare January 30, 2026 18:43
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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants