Skip to content

chore(deps): update dependency @nuxt/kit to 4.0.3 #43

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.

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

Conversation

chrisbbreuer
Copy link
Member

This PR contains the following updates:

npm

Package Change Age Adoption Passing Confidence
@nuxt/kit (source) 3.18.1 -> 4.0.3 age adoption passing confidence

Release Notes

nuxt/nuxt (@nuxt/kit)

3.18.1 -> 4.0.3

v4.0.3

Compare Source

4.0.3 is a regularly scheduled patch release.

👉 Changelog

compare changes

🔥 Performance

  • kit: Get absolute path from tinyglobby in resolveFiles (#32846)

🩹 Fixes

  • nuxt: Do not throw undefined error variable (#32807)
  • vite: Include tsconfig references during typeCheck (#32835)
  • nuxt: Add sourcemap path transformation for client builds (#32313)
  • nuxt: Add warning for lazy-hydration missing prefix (#32832)
  • nuxt: Trigger call once navigation even when no suspense (#32827)
  • webpack: Handle null result from webpack call (84816d8a1)
  • kit,nuxt: Use reverseResolveAlias ...

[View full release notes]

Released by @github-actions[bot] on 8/5/2025

v4.0.2

Compare Source

4.0.2 is the next patch release.

Timetable: 28 July.

👉 Changelog

compare changes

🩹 Fixes

  • nuxt: Provide typed slots for <ClientOnly> and <DevOnly> (#32707)
  • kit,nuxt,schema: Add trailing slash to some dir aliases (#32755)
  • nuxt: Constrain global defineAppConfig type (#32760)
  • kit: Include module types in app context (#32758)
  • nuxt: Include source base url for remote islands (#32772)
  • vite: Use vite node server to transform requests (#32791)
  • kit: Use mlly to parse module paths (#32386)
  • nuxt: Execute all plugins after error rendering error.vue ([#32744](https://gith...

[View full release notes]

Released by @github-actions[bot] on 7/29/2025

v4.0.1

Compare Source

v4.0.1 is the first regularly scheduled patch release of v4

It will be followed up later this week with v3.18, which will backport a number of the features/fixes from Nuxt v4 to v3.

✅ 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

  • nuxt: Add nuxt.schema files to node tsconfig context (#32644)
  • nuxt,vite: Unpin nitropack (ed5ad64ad)
  • nuxt: Expose shared aliases within shared/ dir (#32676)

💅 Refactors

[View full release notes]

Released by @github-actions[bot] on 7/21/2025


📊 Package Statistics

  • @nuxt/kit: 1,896,317 weekly downloads

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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR was generated by Buddy 🤖

Copy link

netlify bot commented Aug 15, 2025

Deploy Preview for ts-maps ready!

Name Link
🔨 Latest commit 6cb2383
🔍 Latest deploy log https://app.netlify.com/projects/ts-maps/deploys/689f22dd9e534500080bb502
😎 Deploy Preview https://deploy-preview-43--ts-maps.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@chrisbbreuer chrisbbreuer deleted the buddy-bot/update-major-update---@nuxt/kit-1755259605406 branch August 20, 2025 10:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants