[Snyk] Fix for 1 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• usage-based-subscriptions/package.json
• usage-based-subscriptions/pnpm-lock.yaml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-AJV-15274295	685

---

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:

🦉 Regular Expression Denial of Service (ReDoS)

[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
✅	Licenses	0	0	0	0	0 issues

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

[snyk-io]

This upgrade contains a major version update for eslint from v8 to v10, which is a high-risk change requiring significant migration effort. The update for next-superjson is considered low-risk.

eslint 8.45.0 → 10.0.0 (High Risk)

This upgrade spans two major versions (v9 and v10) and introduces substantial breaking changes that require developer action. The most critical change is the complete removal of the traditional .eslintrc configuration in favor of the new "flat config" format (eslint.config.js).

Key Breaking Changes:

• Configuration File Migration: You must migrate your existing .eslintrc.js or .eslintrc.json file to the new eslint.config.js format. The old format is no longer supported in v10. ESLint provides a Configuration Migration Guide to assist with this process.
• Node.js Version Requirement: Support for older Node.js versions has been dropped. ESLint v9 requires Node.js v18.18.0+ or v20.9.0+, and ESLint v10 raises the requirement to v20.19.0+.
• Removed/Changed Rules: The valid-jsdoc and require-jsdoc rules have been removed. Other rules, like no-unused-vars, have had their default behavior changed, which may result in new linting errors.
• Removed Formatters: Several built-in formatters like checkstyle, compact, and junit have been removed. If you use a custom formatter, ensure it is still compatible.

Recommendation:
This is a significant migration that should be handled with care. Allocate time to rewrite your configuration using the new eslint.config.js format and test thoroughly. Follow the official ESLint v9 Migration Guide and v10 Migration Guide for detailed instructions.

next-superjson 0.0.4 → 1.0.0 (Low Risk)

This major version upgrade modernizes the package's internals but should not require changes to your configuration.

Highlights:

• The primary change in v1.0.0 is a switch from using a Babel plugin to a more performant SWC plugin to integrate with Next.js.
• The configuration method in next.config.js remains the same.

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