[Snyk] Security upgrade next from 14.2.32 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):

• Custom Error Page/Error Page/package.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
Custom Error Page/Error Page/package.json	0% smaller

[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, automatically generated by Snyk, implements a crucial security upgrade for the next dependency within the Custom Error Page/Error Page/package.json file. The primary goal is to mitigate a high-severity vulnerability concerning resource allocation, thereby bolstering the application's security posture.

Highlights

• Dependency Upgrade: The next dependency has been upgraded from version "14.2.32" to "15.5.10" in Custom Error Page/Error Page/package.json.
• Security Fix: This upgrade addresses a high-severity vulnerability (SNYK-JS-NEXT-15104645) related to "Allocation of Resources Without Limits or Throttling".

🧠 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. ↩

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🔴 Make sure a JIRA issue is mentioned in the title

Waiting for:

• title ~= ^\[\w+-\d+\]

This rule is failing.

Make sure PR title contains a JIRA issue

• title ~= ^\[\w+-\d+\]

🔴 Make sure a JIRA issue is mentioned in the title

Waiting for:

• title ~= ^\[\w+-\d+\]

This rule is failing.

Make sure PR title contains a JIRA issue

• title ~= ^\[\w+-\d+\]

🔴 Enforce conventional commit

Waiting for:

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?:

This rule is failing.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?:

🔴 Force ticket association

Waiting for:

• body ~= Fixes

This rule is failing.

Make sure PR has a ticket associated

• body ~= Fixes

🟠 Merge during working hours

Waiting for:

• schedule = Mon-Fri 09:00-17:00[America/Chicago]

Waiting for schedule condition.

Make sure to merge only during working hours

• schedule = Mon-Fri 09:00-17:00[America/Chicago]

[gemini-code-assist]

Code Review

This pull request upgrades the next package from 14.2.32 to 15.5.10 to fix a security vulnerability. While this is a necessary security update, it's a major version bump that introduces breaking changes. The most critical issue is that Next.js 15 requires React 18, but the project is still on React 17. This incompatibility will likely break the application. I've added a comment with details on how to resolve this.

[gemini-code-assist]

Upgrading next to a new major version (15.x) introduces breaking changes. Next.js versions 14 and later require React 18.2.0 or newer. This project is currently using React 17.0.2, which is incompatible and will likely cause the application to break.

To resolve this, you should also upgrade react, react-dom, and their corresponding types in your package.json:

"dependencies": {
  "@types/react": "^18.0.0",
  "next": "15.5.10",
  "react": "^18.2.0",
  "react-dom": "^18.2.0",
  ...
},

After updating these dependencies, you may need to address other breaking changes introduced in React 18, such as changes to the root API.

[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.