[Snyk] Security upgrade next from 14.2.35 to 15.5.10

[hashim21223445]

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

Snyk changed the following file(s):

• benchmark/frontend/package.json
• benchmark/frontend/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

---

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

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
benchmark/frontend/package-lock.json	9% smaller
benchmark/frontend/package.json	0% smaller

[snyk-io]

⛔ Snyk checks have failed. 1 issues have been found so far.

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

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

[gemini-code-assist]

Summary of Changes

Hello @hashim21223445, 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 focuses on enhancing the security posture of the benchmark/frontend project by performing a critical upgrade of the next framework to version 15.5.10. This update directly resolves a high-severity vulnerability related to resource allocation, ensuring the application benefits from the latest security patches and stability improvements. The change also propagates necessary updates across several associated dependencies, maintaining compatibility and integrating new features within the Next.js ecosystem.

Highlights

• Security Upgrade: Upgraded the next dependency from version 14.2.35 to 15.5.10 to address a high-severity vulnerability.
• Vulnerability Fixed: This PR specifically fixes the 'Allocation of Resources Without Limits or Throttling' vulnerability (SNYK-JS-NEXT-15104645) in the next package, which had a score of 696.
• Dependency Updates: Numerous internal Next.js related packages, such as @next/env, various @next/swc-* binaries, and @swc/helpers, have been updated to compatible versions. New optional dependencies related to image processing (sharp and its platform-specific modules) were also introduced.
• Peer Dependency Changes: The next package's peer dependencies now support newer React versions (up to ^19.0.0) and include babel-plugin-react-compiler as an optional peer dependency.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 from Snyk upgrades Next.js to v15 to resolve a security vulnerability. This is a major version update with breaking changes. I've added a comment on package.json highlighting two important actions to take: updating your required Node.js version and upgrading eslint-config-next to match the new Next.js version. These changes are crucial for ensuring stability and maintaining code quality.

[gemini-code-assist]

This major upgrade to Next.js v15 has a couple of important implications that should be addressed:

1. Node.js Version Requirement (critical): Next.js 15 requires Node.js ^18.18.0 || ^19.8.0 || >= 20.0.0. To prevent build or runtime failures, I strongly recommend adding an engines field to your package.json to enforce this, for example:

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

2. Outdated eslint-config-next (high): Your eslint-config-next is at version ^13.4.2. This should be upgraded to match the Next.js version (e.g., ^15.5.10) to get the correct linting rules for v15. An outdated configuration might miss new issues or report them incorrectly.