Skip to content

fix(deps): update all major updates (major) #592

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 all major updates (major) #592

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

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

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update
@antfu/eslint-config ^4.11.0 → ^6.0.0 age confidence pnpm.catalog.default major
@iconify/vue (source) ^4.3.0 → ^5.0.0 age confidence pnpm.catalog.default major
@nuxt/kit (source) ^3.16.1 → ^4.0.0 age confidence pnpm.catalog.default major
@nuxt/schema (source) ^3.16.1 → ^4.0.0 age confidence pnpm.catalog.default major
@storybook/addon-links (source) ^8.6.10 → ^10.0.0 age confidence pnpm.catalog.default major
@storybook/vue3 (source) ^8.6.10 → ^10.0.0 age confidence pnpm.catalog.default major
@storybook/vue3-vite (source) ^8.6.10 → ^10.0.0 age confidence pnpm.catalog.default major
@types/jsdom (source) ^21.1.7 → ^27.0.0 age confidence pnpm.catalog.default major
@types/node (source) ^22.13.14 → ^24.0.0 age confidence pnpm.catalog.default major
@vitejs/plugin-vue (source) ^5.2.3 → ^6.0.0 age confidence pnpm.catalog.default major
@vitejs/plugin-vue-jsx (source) ^4.1.2 → ^5.0.0 age confidence pnpm.catalog.default major
@vitest/coverage-v8 (source) ^3.0.9 → ^4.0.0 age confidence pnpm.catalog.default major
@vueuse/core (source) ^13.0.0 → ^14.0.0 age confidence devDependencies major
@vueuse/core (source) ^11.2.0 → ^14.0.0 age confidence dependencies major
actions/cache v4 → v5 age confidence action major
actions/checkout v4 → v6 age confidence action major
actions/setup-node v4 → v6 age confidence action major
amannn/action-semantic-pull-request v5 → v6 age confidence action major
chokidar ^4.0.3 → ^5.0.0 age confidence pnpm.catalog.default major
chromatic (source) ^11.27.0 → ^13.0.0 age confidence pnpm.catalog.default major
eslint-plugin-storybook (source) ^0.12.0 → ^10.0.0 age confidence pnpm.catalog.default major
globby ^14.1.0 → ^16.0.0 age confidence pnpm.catalog.default major
jsdom ^26.0.0 → ^27.0.0 age confidence pnpm.catalog.default major
lint-staged ^15.5.0 → ^16.0.0 age confidence pnpm.catalog.default major
npm-run-all2 ^7.0.2 → ^8.0.0 age confidence pnpm.catalog.default major
nx (source) ^20.6.4 → ^22.0.0 age confidence pnpm.catalog.default major
tailwindcss (source) ^3.4.14 → ^4.0.0 age confidence devDependencies major
unplugin-vue-components ^28.4.1 → ^30.0.0 age confidence pnpm.catalog.default major
vite (source) ^6.1.2 → ^7.0.0 age confidence pnpm.catalog.default major
vite-tsconfig-paths ^5.1.4 → ^6.0.0 age confidence pnpm.catalog.default major
vitest (source) ^3.0.9 → ^4.0.0 age confidence pnpm.catalog.default major
vitest-canvas-mock ^0.3.3 → ^1.0.0 age confidence pnpm.catalog.default major
vue-component-meta (source) ^2.2.8 → ^3.0.0 age confidence devDependencies major
vue-component-meta (source) ^2.1.10 → ^3.0.0 age confidence devDependencies major
vue-sonner ^1.3.0 → ^2.0.0 age confidence pnpm.catalog.default major
vue-tsc (source) ^2.2.8 → ^3.0.0 age confidence pnpm.catalog.default major

Release Notes

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

v6.7.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v6.7.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v6.7.1

Compare Source

   🐞 Bug Fixes
  • pnpm: Do not set catalogMode when catalogs is not enabled  -  by @​antfu (0471e)
    View changes on GitHub

v6.7.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v6.6.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v6.6.0

Compare Source

   🐞 Bug Fixes
  • pnpm: Enforce catalog usage based on smart detection  -  by @​antfu (654c0)
    View changes on GitHub

v6.5.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v6.5.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v6.4.2

Compare Source

   🐞 Bug Fixes
  • pnpm: Move pnpm-workspace.yaml sorting config from yaml to pnpm  -  by @​antfu (fc2b1)
    View changes on GitHub

v6.4.1

Compare Source

No significant changes

    View changes on GitHub

v6.3.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v6.2.0

Compare Source

   🚀 Features
    View changes on GitHub

v6.1.0

Compare Source

   🚀 Features
    View changes on GitHub

v6.0.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v5.4.1

Compare Source

No significant changes

    View changes on GitHub

v5.4.0

Compare Source

No significant changes

    View changes on GitHub

v5.3.0

Compare Source

   🐞 Bug Fixes
  • Use ecmaVersion 'latest' per eslint's docs recommendation. fixes support for import attributes  -  by @​romansp in #​756 (2031b)
    View changes on GitHub

v5.2.2

Compare Source

   🚀 Features
    View changes on GitHub

v5.2.1

Compare Source

No significant changes

    View changes on GitHub

v5.2.0

Compare Source

   🚀 Features
    View changes on GitHub

v5.1.0

Compare Source

   🚀 Features
    View changes on GitHub

v5.0.0

Compare Source

   🚨 Breaking Changes
   🐞 Bug Fixes
    View changes on GitHub

v4.19.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.18.0

Compare Source

   🚀 Features
    View changes on GitHub

v4.17.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.16.2

Compare Source

No significant changes

    View changes on GitHub

v4.16.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.16.0

Compare Source

   🚀 Features
    View changes on GitHub

v4.15.0

Compare Source

   🚀 Features
    View changes on GitHub

v4.14.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.14.0

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.13.3

Compare Source

No significant changes

    View changes on GitHub

v4.13.2

Compare Source

No significant changes

    View changes on GitHub

v4.13.1

Compare Source

No significant changes

    View changes on GitHub

v4.13.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.12.1

Compare Source

No significant changes

    View changes on GitHub

v4.12.0

Compare Source

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

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
  • Add --pnpm flag to correctly publish prerelease (#​33688)
  • Update action lint config (#​33710)
❤️ 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
  • Fix typo in eslint flat config description (#​33569)
  • Add signal support to useAsyncData examples (#​33601)
  • Document pending as alias of status === 'pending' (#​33221)
  • Note that cookieStore is true by default (#​33572)
  • Add information on types for server context (#​33511)
  • Mark webstorm issue resolved (#​33608)
  • Clarify route middleware doesn't affect API routes (#​33643)
  • Improve docs for useHead/useHydration/useLazy* (#​33626)
  • Update link to nitro source to v2 branch (08018af4f)
  • Add typescript documentation for module authors (#​33637)
  • Typo (#​33655)
🏡 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). This architectural change allows for different Nitro integration patterns and paves the way for future innovations in server-side rendering.

While this change is mostly internal, it's part of our ongoing effort to make Nuxt more modular and flexible. The new package provides standalone Nitro integration and sets the foundation for alternative integration approaches (such as using Nitro as a Vite plugin in Nuxt v5+).

[!NOTE]
This is an internal refactor – no changes should be required in your code.

⚡ Performance Improvements

We've also shipped several performance enhancements:

  • Precomputed renderer dependencies – We now compute renderer dependencies at build time rather than runtime, improving cold start and initial render performance (#​33361)
  • Reduced dependencies – Removed unnecessary dependencies from kit and schema packages (7ae2cf563)
📉 Async Data Handler Extraction

One of the most exciting performance improvements is the new experimental async data handler extraction (#​33131). When enabled, handler functions passed to useAsyncData and useLazyAsyncData are automatically extracted into separate chunks and dynamically imported.

This is particularly effective for prerendered static sites, as the data fetching logic is only needed at build time and can be completely excluded from the client bundle.

[!NOTE]
In testing with a previous version of nuxt.com, this feature reduced JavaScript bundle size by 39%! Of course, your mileage may vary depending on how much data fetching logic you have.

<script setup lang="ts">
// This handler will be extracted into a separate chunk
// and only loaded when needed
const { data: post } = await useAsyncData('post', async () => {
  const content = await queryContent(`/blog/${route.params.slug}`).findOne()
  
  // Complex data processing that you don't want in the client bundle
  const processed = await processMarkdown(content)
  const related = await findRelatedPosts(content.tags)
  
  return {
    ...processed,
    related
  }
})
</script>

For static/prerendered sites, enable it in your config:

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

The extracted handlers are then tree-shaken from your client bundle when prerendering, as the data is already available in the

Configuration

📅 Schedule: Branch creation - "every 6 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.

@github-actions
Copy link
Contributor

github-actions bot commented Jul 1, 2025 •
edited
Loading

Thank you for following the naming conventions! 🙏

@renovate renovate bot force-pushed the renovate/major-all-major branch from 6739711 to c674396 Compare July 1, 2025 19:42
@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Jul 1, 2025 •
edited
Loading

Deploying primitives-oku-ui with  Cloudflare Pages  Cloudflare Pages

Latest commit: 7d2cd69
Status:🚫  Build failed.

View logs

@renovate renovate bot force-pushed the renovate/major-all-major branch 3 times, most recently from b4e291a to 427370d Compare July 22, 2025 14:43
@renovate renovate bot force-pushed the renovate/major-all-major branch 8 times, most recently from 88ecf4f to 71f2d09 Compare July 28, 2025 18:53
@renovate renovate bot force-pushed the renovate/major-all-major branch 9 times, most recently from a98c554 to e5cec25 Compare August 13, 2025 15:38
@renovate renovate bot force-pushed the renovate/major-all-major branch 7 times, most recently from 4e68610 to cd102ab Compare August 19, 2025 16:09
@renovate renovate bot force-pushed the renovate/major-all-major branch 18 times, most recently from 385b84b to 70a99b7 Compare December 19, 2025 17:51
@renovate renovate bot force-pushed the renovate/major-all-major branch 6 times, most recently from cd2619a to 7814811 Compare December 26, 2025 16:34
@renovate renovate bot force-pushed the renovate/major-all-major branch 3 times, most recently from 1e62f49 to b9049e7 Compare January 5, 2026 16:59
@renovate renovate bot force-pushed the renovate/major-all-major branch from b9049e7 to 8ff99bf Compare January 5, 2026 20:56
@renovate renovate bot force-pushed the renovate/major-all-major branch from 8ff99bf to 7d2cd69 Compare January 7, 2026 09:51
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

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant