Skip to content

[Snyk] Security upgrade eslint from 7.32.0 to 9.1.0 - #197

Open
snyk-io[bot] wants to merge 1 commit into
masterfrom
snyk-fix-4a025a9279c07f749418b39859b2c066
Open

[Snyk] Security upgrade eslint from 7.32.0 to 9.1.0#197
snyk-io[bot] wants to merge 1 commit into
masterfrom
snyk-fix-4a025a9279c07f749418b39859b2c066

Conversation

@snyk-io

@snyk-io snyk-io Bot commented Feb 27, 2026

Copy link
Copy Markdown

snyk-top-banner

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

Snyk changed the following file(s):

  • chargebee-js-react/package.json
  • chargebee-js-react/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Inefficient Algorithmic Complexity
SNYK-JS-MINIMATCH-15353389
  710  

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.

…k.json to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-MINIMATCH-15353389
@snyk-io

snyk-io Bot commented Feb 27, 2026

Copy link
Copy Markdown
Author

Merge Risk: High

This upgrade spans two major versions (v7 to v9) and introduces significant breaking changes that require mandatory configuration and code updates.

Key Breaking Changes:

  • New Configuration System (v9): ESLint v9 introduces a new default configuration format, eslint.config.js (also known as "flat config"). The traditional .eslintrc.* file format is now deprecated. You must migrate your existing configuration to the new format. A migration tool is available (npx @eslint/migrate-config) to assist with this process.
  • Node.js API Changes (v8): The CLIEngine class was removed in v8 and replaced with the ESLint class. Any scripts or tools that programmatically invoke ESLint must be updated to use the new API.
  • Node.js Version Support: Support for older Node.js versions has been dropped. ESLint v8 requires Node.js ^12.22.0, ^14.17.0, or >=16.0.0. ESLint v9 requires Node.js v18.18.0 or higher.
  • Rule and Formatter Changes:
    • Several core formatters (codeframe, table, compact, junit, etc.) have been removed and must be installed as separate packages if needed.
    • The require-jsdoc and valid-jsdoc rules were removed in v9 and should be replaced with eslint-plugin-jsdoc.
    • The eslint:recommended configuration has been updated in both v8 and v9, which may introduce new linting errors.

Recommendation: This upgrade requires a significant migration effort. It is critical to migrate your configuration to the new eslint.config.js format and update any custom integrations that use the Node.js API. Thoroughly test your linting setup after the upgrade to address new errors from rule changes.

Sources:

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

@snyk-io

snyk-io Bot commented Feb 27, 2026

Copy link
Copy Markdown
Author

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.

@hivel-marco hivel-marco Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Complexity Score: 2.3 - Simple

View Breakdown
  • Lines Changed: 1036
  • Files Changed: 2
  • Complexity Added: 0
  • Raw Score: 26.72

Secrets found in the following files: chargebee-js-react/package-lock.json
PII found in the following files: chargebee-js-react/package-lock.json

  • Bumps the wrapper package version from 0.6.7 to 0.6.8.
  • Upgrades ESLint from ^7.11.0 to ^9.1.0 to align with the latest linting ecosystem.
  • Refreshes and restructures ESLint-related transitive dependencies in package-lock.json (e.g., @eslint/eslintrc, @eslint/js, espree, eslint-scope, esquery, file-entry-cache, flat-cache, etc.).
  • Removes older, now-unused linting support packages and introduces new ones required by ESLint 9 (e.g., @eslint-community/eslint-utils, @eslint-community/regexpp, @humanwhocodes/*, @nodelib/fs.*, find-up, keyv, etc.).
  • Updates various dependency versions and engine requirements to be compatible with ESLint 9’s minimum Node version (>= 18.18.0 in several places).

Overall, this PR is a tooling/maintenance update focused on modernizing the linting stack and incrementing the package version, with no runtime code changes to the React wrapper itself.

File-level change summary

File Change Summary
chargebee-js-react/package.json Updates devDependencies.eslint from ^7.11.0 to ^9.1.0 to use the latest ESLint major version.
chargebee-js-react/package-lock.json Bumps package version to 0.6.8; regenerates lockfile to reflect ESLint 9 upgrade and its dependency graph, including new ESLint core packages, updated parser/tooling libs, and removal of obsolete lint-related dependencies.

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.

0 participants