build(deps-dev): bump eslint from 9.39.1 to 10.0.2#165
Conversation
Bumps [eslint](https://github.com/eslint/eslint) from 9.39.1 to 10.0.2. - [Release notes](https://github.com/eslint/eslint/releases) - [Commits](eslint/eslint@v9.39.1...v10.0.2) --- updated-dependencies: - dependency-name: eslint dependency-version: 10.0.2 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
| "@types/node": "^24.3.0", | ||
| "@typescript-eslint/parser": "^8.31.1", | ||
| "eslint": "^9.25.1", | ||
| "eslint": "^10.0.2", |
There was a problem hiding this comment.
ESLint 10 breaks legacy eslintrc configuration format
High Severity
ESLint 10 completely removed eslintrc support, requiring flat config (eslint.config.js) instead. The project still has an eslintrc.json using the legacy format (with parser, env, extends, parserOptions, rules). This configuration will be entirely ignored by ESLint 10, causing any ESLint invocation to run with no rules or to error out. The config also extends airbnb/base, which relies on the removed eslintrc system.
| "integrity": "sha512-xJBAbDifo5hpffDBuHl0Y8ywswbiAp/Wi7Y/GtAgSlZyIABppyurxVueOPE8LUQOxdlgi6Zqce7uoEpqNTeiUw==", | ||
| "dev": true, | ||
| "license": "MIT" | ||
| }, |
There was a problem hiding this comment.
Parser peer dependency incompatible with ESLint 10
High Severity
The locked @typescript-eslint/parser version 8.46.2 declares peerDependencies of "eslint": "^8.57.0 || ^9.0.0", which does not include ESLint 10. The semver range ^9.0.0 only covers >=9.0.0 <10.0.0. Support for ESLint 10 was only added in @typescript-eslint/parser v8.56.0+, but the lockfile pins an older version that is explicitly incompatible.


Bumps eslint from 9.39.1 to 10.0.2.
Release notes
Sourced from eslint's releases.
... (truncated)
Commits
55122d610.0.280f1e29Build: changelog update for 10.0.2951223bchore: update dependency@eslint/eslintrcto ^3.3.4 (#20553)13eeedbdocs: link rule type explanation to CLI option --fix-type (#20548)6aa1afechore: update dependency eslint-plugin-jsdoc to ^62.7.0 (#20536)2b72361fix: updateajvto6.14.0to address security vulnerabilities (#20537)98cbf6bdocs: update migration guide per Program range change (#20534)61a2405docs: add missing semicolon in vars-on-top rule example (#20533)0bd549710.0.1ddb80efBuild: changelog update for 10.0.1You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Note
Medium Risk
Upgrading to ESLint v10 can introduce breaking changes in lint behavior and requires newer Node versions, which may break CI or local dev environments if they aren’t aligned.
Overview
Updates the dev tooling by bumping
eslintfrom v9 to v10 (^10.0.2) and regenerating the lockfile to pull in the new ESLint dependency tree.The lockfile changes include security-related dependency bumps (e.g.,
ajvandminimatch) and updated transitive packages/metadata consistent with ESLint v10.Written by Cursor Bugbot for commit 0e51ef0. This will update automatically on new commits. Configure here.