-
Notifications
You must be signed in to change notification settings - Fork 169
chore(deps): update dependency eslint to v10 #2231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
This PR is being reviewed by Cursor Bugbot
Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
Comment @cursor review or bugbot run to trigger another review on this PR
| "bats": "^1.13.0", | ||
| "cross-env": "^10.0.0", | ||
| "eslint": "^9.32.0", | ||
| "eslint": "^10.0.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ESLint v10 incompatible with multiple plugin peer dependencies
High Severity
Upgrading eslint to ^10.0.0 breaks peer dependency contracts with several plugins used in this project. typescript-eslint v8.53.0 declares eslint: "^8.57.0 || ^9.0.0", eslint-plugin-react v7.37.5 declares eslint: "^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7", and @apify/eslint-config declares eslint: "^9.19.0". None of these ranges include v10. Since ESLint v10 is a major release with breaking API changes (removed @eslint/eslintrc, @eslint/js, chalk, lodash.merge; upgraded espree, eslint-scope, eslint-visitor-keys to new majors), these plugins are likely to fail at runtime.
Additional Locations (1)
| "bats": "^1.13.0", | ||
| "cross-env": "^10.0.0", | ||
| "eslint": "^9.32.0", | ||
| "eslint": "^10.0.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ESLint v10 Node.js requirement conflicts with project engines
Medium Severity
The project declares engines.node: ">=18.0.0" but eslint v10 requires node: "^20.19.0 || ^22.13.0 || >=24", dropping Node 18 support entirely. Any CI/CD environments or developers running Node 18 will be unable to use eslint after this upgrade. Either the project's engine constraint needs updating or the eslint upgrade needs to wait until Node 18 is fully dropped from the project.
|
Preview for this PR was built for commit |
ad1300b to
0ec49d1
Compare
|
Preview for this PR was built for commit |
0ec49d1 to
9f2b329
Compare
|
Preview for this PR was built for commit |
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |


This PR contains the following updates:
^9.32.0β^10.0.0Release Notes
eslint/eslint (eslint)
v10.0.0Compare Source
Configuration
π Schedule: Branch creation - "every weekday" (UTC), Automerge - At any time (no schedule defined).
π¦ Automerge: Disabled by config. Please merge this manually once you are satisfied.
β» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
π Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.