[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	Score
	Infinite loop SNYK-JS-BRACEEXPANSION-15789759	641

---

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 project’s Nuxt dependency to remediate a reported transitive vulnerability, updating npm manifests/lockfile accordingly.

Changes:

• Bump nuxt from ^3.16.2 to ^3.20.0 in package.json.
• Refresh package-lock.json to reflect the Nuxt upgrade and updated transitive dependency graph.

Reviewed changes

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

File	Description
package.json	Updates Nuxt version to the Snyk-suggested fixed release.
package-lock.json	Locks Nuxt 3.20.0 and updates transitive dependencies for the security remediation.

---

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

[Copilot]

Upgrading to nuxt ^3.20.0 introduces a Node.js engine requirement mismatch: package-lock.json shows nuxt@3.20.0 requires Node "^20.19.0 || >=22.12.0", but this repo pins "engines.node" to 16. This will cause installs/builds to fail in environments honoring engines (and likely at runtime). Please either bump the project's required Node version (and align CI/deploy) or pin Nuxt to the latest version that supports Node 16.