Skip to content

[Snyk] Security upgrade eslint from 8.57.1 to 10.0.0 - #153

Open
adamlaska wants to merge 1 commit into
mainfrom
snyk-fix-8ab01fe1324507785b341cc3f34e76fb
Open

adamlaska wants to merge 1 commit into
mainfrom
snyk-fix-8ab01fe1324507785b341cc3f34e76fb

Conversation

@adamlaska

Copy link
Copy Markdown
Owner

snyk-top-banner

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

Snyk changed the following file(s):

  • 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
high severity Inefficient Algorithmic Complexity
SNYK-JS-BRACEEXPANSION-17706650

Breaking Change Risk

Merge Risk: High

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.

@adamlaska

Copy link
Copy Markdown
Owner Author

Merge Risk: High

This upgrade from ESLint v8 to v10 is a major transition with significant breaking changes, requiring a complete overhaul of your configuration.

Key Breaking Changes:

  • Mandatory Configuration Migration: The legacy configuration system using .eslintrc.* files is completely removed in v10.0.0. You must migrate your entire configuration to the new "flat config" format (eslint.config.js), which was introduced as the default in v9. This is a substantial change requiring a full rewrite of your ESLint setup.

  • Node.js Version Requirement: Support for older Node.js versions has been dropped. ESLint v10.0.0 requires Node.js v20.19.0 or newer. The upgrade to v9 had already required Node.js v18.18.0+.

  • Removed Rules and Formatters: The require-jsdoc and valid-jsdoc rules were removed in v9. Additionally, several formatters (including checkstyle, junit, compact) were removed, with only stylish, html, json, and json-with-meta remaining.

  • Configuration Discovery Change: v10 introduces a new configuration file lookup algorithm that searches for eslint.config.js starting from the directory of each linted file, which primarily affects monorepo setups.

Sources:

Recommendation: This is a high-effort upgrade that cannot be completed without significant manual intervention. Developers must rewrite the project's ESLint configuration from the legacy .eslintrc format to the new eslint.config.js flat config format before this upgrade can be merged.

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

@google-cla

google-cla Bot commented Jul 1, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants