Skip to content

chore(deps): update nuxt to v4.0.3 - autoclosed #1325

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

Closed
wants to merge 1 commit into from
Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 22, 2025

This PR contains the following updates:

Package Change Age Confidence
@nuxt/webpack-builder (source) 4.0.2 -> 4.0.3 age confidence
nuxt (source) 4.0.2 -> 4.0.3 age confidence

Release Notes

nuxt/nuxt (@​nuxt/webpack-builder)

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 for better errors (#​32853)
📖 Documentation
  • Fix publicDir alias (#​32841)
  • Mention bun.lock for lockfile (#​32820)
  • Add a section about augmenting types with TS project references (#​32843)
  • Improve explanation of global middleware (#​32855)
🏡 Chore
✅ Tests
  • Move tests for defineNuxtComponent out of e2e test (#​32848)
🤖 CI
  • Move nightly releases into different concurrency group (664041be7)
❤️ Contributors

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 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.

@renovate renovate bot force-pushed the renovate/nuxt branch from 7653771 to 20cb140 Compare July 24, 2025 10:49
@renovate renovate bot changed the title chore(deps): update devdependency @nuxt/eslint to v1.7.0 chore(deps): update devdependency @nuxt/eslint to v1.7.1 Jul 24, 2025
@renovate renovate bot force-pushed the renovate/nuxt branch from 20cb140 to 7044ef8 Compare July 25, 2025 11:26
@renovate renovate bot changed the title chore(deps): update devdependency @nuxt/eslint to v1.7.1 chore(deps): update nuxt Jul 25, 2025
@renovate renovate bot force-pushed the renovate/nuxt branch 2 times, most recently from 820e0be to e826fce Compare July 30, 2025 10:02
@renovate renovate bot changed the title chore(deps): update nuxt chore(deps): update nuxt - autoclosed Jul 31, 2025
@renovate renovate bot closed this Jul 31, 2025
@renovate renovate bot deleted the renovate/nuxt branch July 31, 2025 18:05
@renovate renovate bot changed the title chore(deps): update nuxt - autoclosed chore(deps): update nuxt Aug 5, 2025
@renovate renovate bot reopened this Aug 5, 2025
@renovate renovate bot force-pushed the renovate/nuxt branch from d731200 to e826fce Compare August 5, 2025 09:05
@renovate renovate bot changed the title chore(deps): update nuxt chore(deps): update nuxt to v4.0.3 Aug 5, 2025
@renovate renovate bot force-pushed the renovate/nuxt branch from e826fce to e24f3d9 Compare August 5, 2025 13:36
@renovate renovate bot changed the title chore(deps): update nuxt to v4.0.3 chore(deps): update nuxt to v4.0.3 - autoclosed Aug 5, 2025
@renovate renovate bot closed this Aug 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants