You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a major version upgrade to ESLint v10, which introduces significant and mandatory breaking changes. Action is required to upgrade.
Key Breaking Changes:
Complete Removal of eslintrc: Support for the traditional .eslintrc.* configuration file format has been completely removed. All users must migrate to the eslint.config.js (flat config) format. .eslintignore files are also no longer supported and patterns must be moved into the flat config file.
Node.js Version Requirement: Support for Node.js versions older than v20.19.0 has been dropped. You must be on Node.js v20.19.0+, v22.13.0+, or v24+ to use ESLint v10.
New Config File Lookup: A new configuration file lookup algorithm is now the default, which searches for eslint.config.js starting from the directory of each linted file. This is particularly useful for monorepos but may change behavior for some projects.
JSX Reference Tracking: ESLint now properly tracks JSX element references, which may lead to new linting errors for unused imports or undefined components in JSX files.
Recommendation:
This upgrade requires a mandatory migration of your ESLint configuration from the legacy .eslintrc format to the modern eslint.config.js (flat config) format. You must also ensure your environment is running a supported version of Node.js.
Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
packages/koa-access/package.jsonpackages/koa-access/package-lock.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-AJV-15274295
Breaking Change Risk
Important
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)