[Snyk] Security upgrade eslint from 9.39.5 to 10.0.0

[w3nl]

Snyk has created this PR to fix 1 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
	Inefficient Algorithmic Complexity SNYK-JS-JSYAML-18313070

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[w3nl]

This major upgrade to ESLint v10 introduces significant and mandatory breaking changes. All projects must migrate to the new "flat config" format (eslint.config.js), as support for the legacy .eslintrc.* configuration files has been completely removed.

Key Breaking Changes:

• Node.js Requirement: Support for Node.js versions older than v20.19.0 has been dropped.
• Configuration Overhaul: The legacy .eslintrc configuration system is no longer supported. You must migrate to a eslint.config.js file. ESLint provides codemods to help automate this transition.
• New Config Lookup Algorithm: ESLint now locates the configuration file by searching up from the directory of each linted file, which improves behavior in monorepos.
• API Removals: Deprecated methods on the context and SourceCode objects have been removed, which will affect custom rules and plugins.
• Updated Rules: The eslint:recommended ruleset has been updated, which may result in new linting errors after upgrading.

Recommendation:
This upgrade requires significant action. Do not merge until you have:

1. Ensured your environment is running Node.js v20.19.0 or newer.
2. Migrated your project's configuration from .eslintrc to the eslint.config.js flat config format. Review the official migration guide and consider using the provided codemods.

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

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1f7e846d-d485-46b7-88c2-80df09c521b5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch snyk-fix-e877f8ba7091b4743b6da395cf8c6304

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[w3nl]

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

Status	Scan Engine	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.