[Snyk] Fix for 2 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• payment-components/next-js/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
	Allocation of Resources Without Limits or Throttling SNYK-JS-NEXT-15104645	610
	Uncontrolled Recursion SNYK-JS-ESLINT-15102420	505

---

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

[snyk-io]

⚠️ Snyk checks are incomplete.

Status	Scanner	Critical	High	Medium	Low	Total (0)
⚠️	Open Source Security	0	0	0	0	See details
⚠️	Licenses	0	0	0	0	See details

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

[snyk-io]

This upgrade contains major breaking changes across eslint, next, and eslint-config-next, requiring significant configuration and code modifications.

• eslint (8.57.1 → 9.26.0): High risk. This major upgrade requires a migration from the legacy .eslintrc config file to the new eslint.config.js (flat config) format. It also drops support for Node.js versions below 18.18.0 and removes several core rules and formatters.

• next (14.2.13 → 15.5.10): High risk. Next.js 15 introduces several breaking changes, including requiring React 19, making previously synchronous APIs like cookies() and headers() asynchronous, and changing caching defaults to be uncached for fetch and GET Route Handlers. The next lint command is also being deprecated.

• eslint-config-next (14.2.13 → 15.0.0): Medium risk. This upgrade adds support for ESLint 9 and its new flat config structure. Projects must migrate their ESLint configuration to be compatible.

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