[Snyk] Security upgrade next from 15.5.9 to 16.1.5

[Dargon789]

Snyk has created this PR to fix 2 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
	Allocation of Resources Without Limits or Throttling SNYK-JS-NEXT-15104645	696
	Allocation of Resources Without Limits or Throttling SNYK-JS-NEXT-15105315	696

---

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:

🦉 Allocation of Resources Without Limits or Throttling

[Dargon789]

❌ Deploy Preview for heroic-nougat-6c8a7f failed. Why did it fail? →

Name	Link
🔨 Latest commit	18857b8
🔍 Latest deploy log	https://app.netlify.com/projects/heroic-nougat-6c8a7f/deploys/697e904f3322bb000882b15d

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gemini-code-assist]

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly improves the project's security posture by performing a critical upgrade of the next framework and its associated ecosystem of dependencies. The primary motivation is to mitigate two high-severity vulnerabilities related to resource allocation, ensuring the application remains robust and protected against potential exploits. This update also brings the project up to date with the latest recommended versions of several core libraries, enhancing overall stability and maintainability.

Highlights

• Dependency Upgrade: Next.js: The core Next.js framework has been upgraded from version "15.5.9" to "16.1.5" to incorporate the latest features and security patches.
• Vulnerability Resolution: This pull request addresses and fixes two high-severity 'Allocation of Resources Without Limits or Throttling' vulnerabilities (SNYK-JS-NEXT-15104645 and SNYK-JS-NEXT-15105315) found in the next dependency, enhancing the project's security posture.
• Transitive Dependency Updates: Numerous related dependencies, including @emnapi/runtime, various @img/sharp-* and @next/swc-* packages, have been updated to their latest stable versions to ensure compatibility and further improve security.
• Sharp Dependency Refactoring: The sharp image processing library's internal dependencies have been refactored, removing several direct color related packages and introducing @img/colour for improved management.
• Node.js Engine Requirement Update: The minimum Node.js engine requirement for the next dependency has been updated to >=20.9.0, aligning with the latest recommendations and ensuring optimal performance and compatibility.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, upgrades the next package from version 15.5.9 to 16.1.5 to resolve two high-severity vulnerabilities. This is a major version upgrade, which introduces breaking changes. One significant change is the updated Node.js version requirement. I've added a comment regarding this. Please ensure thorough testing is conducted to verify that the application functions as expected after this major dependency upgrade.

[gemini-code-assist]

Upgrading next to 16.1.5 changes its Node.js requirement to >=20.9.0. Your project's engines field in package.json is currently set to >=20, which is less specific. This mismatch could lead to issues in environments that enforce the engines constraint. To prevent this, I recommend updating your engines field to match the new requirement:

"engines": {
  "node": ">=20.9.0"
}