chore(deps): update dependency nuxt to v3.9.1 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
nuxt (source)	3.9.0 -> 3.9.1

---

Release Notes

nuxt/nuxt (nuxt)

v3.9.1

Compare Source

3.9.1 is a regularly scheduled patch release.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the vue and unjs ecosystems.

👉 Changelog

compare changes

🔥 Performance

• nuxt: Avoid multiple iterations in useRequestHeaders (#​24853)
• kit,schema,nuxt: Refactor startsWith to array access (#​24744)
• nuxt: Use single iteration when normalising routes (#​24946)
• nuxt: Remove some line breaks when rendering html (#​24888)

🩹 Fixes

• nuxt: Catch error in NuxtErrorBoundary with ssr: false (#​24896)
• kit: Show correct error when module can't be loaded (#​24957)
• nuxt: Deeply watch island props (#​24986)
• nuxt: Don't show transition on initial page load (#​24935)
• nuxt: Clone cookie to detect changes within object (#​25007)
• nuxt: Do not warn about missing layouts on error page (#​25008)
• nuxt: Ignore plugins typed as any in inferred injections (#​25010)
• nuxt: Reuse intermediate setup state in <ClientOnly> (#​25009)
• nuxt: Skip scanning layout/middleware without name (#​25015)
• nuxt: Wrap universal router currentRoute in Ref (#​25026)
• nuxt: Stop loading indicator if page keys are the same (#​24931)

💅 Refactors

• nuxt: Remove old reference to nuxt-config-schema (#​25067)

📖 Documentation

• Switch features/future docs (f5676fba5)
• Corrected json syntax in 7.esm.md (#​24937)
• Specify yarn pnp opt-out for install (#​24923)
• Capitalise hash for vue-router docs link (#​24948)
• Add badge for callOnce utility (792cf6713)
• Warn about hydration issue with URL fragment (#​24961)
• Mention readValidatedBody and getValidatedQuery (#​24990)
• Add missing imports for nitro examples (#​25003)
• Add an example of provide with object syntax plugins (#​24993)
• Update EOL date for Nuxt 2 (afbc4080b)
• Add callout for getValidatedRouterParams (#​25057)
• Warn about ref unwrapping when providing refs from plugin (#​25054)

🏡 Chore

• Add bullet for adding tests in pr template (2bda817ea)

✅ Tests

• Add missing payload checks (#​24899)
• Start listening for requests earlier (#​24985)

❤️ Contributors

• Pooya Parsa (@​pi0)
• Julien Huang (@​huang-julien)
• Michael Brevard (@​GalacticHypernova)
• Luke Nelson (@​luc122c)
• Alex Liu (@​Mini-ghost)
• Daniel Roe (@​danielroe)
• Alireza Jahandideh (@​Youhan)
• Mateusz Kulpa (@​mateuszkulpa)
• Bernhard Berger (@​bernhardberger)
• Peter (@​tada5hi)
• Sébastien Chopin (@​Atinux)
• heygsc (@​heygsc)
• Clément Ollivier (@​clemcode)
• Soheil Nazari (@​s0h311)
• Alexander Lichter (@​manniL)

---

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.

🔕 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 has been generated by Mend Renovate. View repository job log here.

[github-actions]

❌ @renovate[bot] the signed-off-by was not found in the following 1 commits:

• 5ac27b4: chore(deps): update dependency nuxt to v3.9.1

📝 What should I do to fix it?

All proposed commits should include a sign-off in their messages, ideally at the end.

❔ Why it is required

The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:

By making a contribution to this project, I certify that:

a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.

This is my commit message

Signed-off-by: Random Developer <[email protected]>

Git even has a -s command line option to append this automatically to your commit message:

$ git commit -s -m 'This is my commit message'

[github-actions]

❌ @renovate[bot] the signed-off-by was not found in the following 1 commits:

• 5ac27b4: chore(deps): update dependency nuxt to v3.9.1

📝 What should I do to fix it?

All proposed commits should include a sign-off in their messages, ideally at the end.

❔ Why it is required

The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:

By making a contribution to this project, I certify that:

a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.

This is my commit message

Signed-off-by: Random Developer <[email protected]>

Git even has a -s command line option to append this automatically to your commit message:

$ git commit -s -m 'This is my commit message'