[Snyk] Security upgrade nuxt from 3.16.2 to 3.20.0

[hakatashi]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue
	Infinite loop SNYK-JS-BRACEEXPANSION-15789759

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[Copilot]

Pull request overview

This Snyk-generated PR upgrades the Nuxt dependency to remediate a reported vulnerability (SNYK-JS-BRACEEXPANSION-15789759) by updating the project’s npm dependency graph.

Changes:

• Bump nuxt from ^3.16.2 to ^3.20.0.
• Update package-lock.json to reflect the new resolved Nuxt dependency tree.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File	Description
package.json	Updates the Nuxt version requirement to ^3.20.0.
package-lock.json	Refreshes the lockfile to the Nuxt 3.20.0 resolution (including updated transitive deps/engine constraints).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Upgrading to nuxt ^3.20.0 appears to introduce a Node.js engine requirement of ^20.19.0 || >=22.12.0 (see package-lock.json entry for node_modules/nuxt), while this repo declares "engines.node": "16". This will likely break installs/builds in environments still using Node 16; either bump the project's required Node version (and CI/runtime) accordingly, or choose a Nuxt version compatible with the currently supported Node range.