[Snyk] Fix for 1 vulnerabilities

[kevin-benton]

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

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Incomplete List of Disallowed Inputs SNYK-JS-UNHEAD-15965923	109

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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.

[kevin-benton]

This update includes a major version upgrade for @nuxt/content from v2 to v3, which is a complete rewrite with significant breaking changes. The nuxt core package also has a minor version bump that includes major updates to underlying dependencies.

@nuxt/content 2.13.4 → 3.0.0 (High Risk)

This is a major migration that will require significant developer effort. The library was rebuilt from the ground up, moving to an SQL-based storage system and introducing a new API.

Key Breaking Changes:

• New Data Fetching API: The queryContent() composable has been removed and replaced by queryCollection(). All data fetching logic must be refactored.
• Component Overhaul: The <ContentDoc>, <ContentList>, and <ContentNavigation> components have been removed. All content rendering must now use the unified <ContentRenderer> component.
• Document-Driven Mode Removed: Files in the content/ directory will no longer automatically create pages. You must now create pages manually and use the new APIs to fetch and render content.
• Component Registration: Components under components/content/ are no longer globally registered and must be registered manually if used outside of markdown files.

Recommendation:
This upgrade is a major refactoring effort. Developers must follow the official migration guide closely to update all data queries, components, and routing logic. This should be handled in a separate, dedicated effort before merging.

nuxt 3.13.2 → 3.16.0 (Medium Risk)

While this is a minor version upgrade for Nuxt itself, it introduces major version updates for key dependencies, which could cause issues.

Key Changes:

• Vite 6 Upgrade: Version 3.15 incorporates Vite 6. While the Nuxt team aimed for a non-breaking transition, a major bundler update always carries some risk.
• Dependency Upgrades: Version 3.16 includes major ESM-only versions of core unjs dependencies like unhead v2.
• Potential Styling Issues: There are reports of this upgrade breaking Tailwind CSS styles, requiring manual changes to the tailwind.config.js file.

Recommendation:
After upgrading, developers should verify that their application builds and functions as expected, paying close attention to styling and any custom Vite or Nitro configurations. Test the application thoroughly in a staging environment.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.