[Snyk] Security upgrade eslint from 8.57.0 to 10.0.0

[qbey]

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

Snyk changed the following file(s):

• packages/eslint-config-custom/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-BRACEEXPANSION-18313044	710
	Inefficient Algorithmic Complexity SNYK-JS-JSYAML-18313070	710

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:

🦉 Allocation of Resources Without Limits or Throttling

[qbey]

This is a significant upgrade, spanning two major versions from ESLint v8 to v10. It introduces substantial breaking changes that require mandatory developer action, primarily centered around the configuration system and Node.js version support.

Key Breaking Changes in v9.0.0

• New Default Configuration: The "flat config" format (eslint.config.js) becomes the default, and the legacy .eslintrc format is deprecated. While v9 allowed temporary use of the old format via an environment variable, migration is strongly encouraged. [2, 5, 8]
• Node.js Support Dropped: Support for Node.js versions older than 18.18.0 and v19 is removed. [2, 5]
• Removed Components: Several core formatters (like checkstyle, compact, junit) and the require-jsdoc and valid-jsdoc rules have been removed. [2, 5, 7]

Key Breaking Changes in v10.0.0

• Legacy Config Removed: Support for the .eslintrc configuration format is completely removed. The ESLINT_USE_FLAT_CONFIG flag is no longer honored, making migration to eslint.config.js mandatory. [3, 4, 6, 9]
• Node.js Support Dropped: Requires Node.js v20.19.0 or later. [1, 3, 6]
• New Config Lookup: The engine now locates configuration files starting from the directory of the file being linted, which is a change from the previous behavior of using the current working directory. [1, 3, 6]
• eslint-env Comments: Using /* eslint-env */ comments will now cause linting errors. [1, 3, 4]

Recommendation:
This upgrade cannot be performed automatically. Developers must:

1. Manually migrate the existing .eslintrc configuration to the new eslint.config.js flat config format.
2. Ensure the project's Node.js version is updated to at least v20.19.0.
3. Review and update any custom rules, plugins, or formatters for compatibility with the new versions.

Source: ESLint v9 Migration Guide, ESLint v10 Migration Guide

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