Skip to content

chore(deps): update eslint monorepo to v10 (major) #204

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.

Sign up for GitHub

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

Open
renovate-sh-app wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −2
Open

chore(deps): update eslint monorepo to v10 (major) #204

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions example/webview_demo/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,11 +18,11 @@
"react-dom": "^19.2.0"
},
"devDependencies": {
"@eslint/js": "^9.39.1",
"@eslint/js": "^10.0.0",
"@types/react": "^19.2.7",
"@types/react-dom": "^19.2.3",
"@vitejs/plugin-react": "^5.1.1",
"eslint": "^9.39.1",
"eslint": "^10.0.0",
Copy link
Copy Markdown

@cursor cursor bot Apr 9, 2026

Choose a reason for hiding this comment

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

Lockfile not updated after package.json version bump

Medium Severity

The package.json bumps eslint and @eslint/js to ^10.0.0, but the package-lock.json still references ^9.39.1 for both packages. This mismatch means npm ci will fail because the lockfile is out of sync with package.json. The lockfile needs to be regenerated to reflect the updated dependency ranges.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit bbeb576. Configure here.

Copy link
Copy Markdown

@cursor cursor bot Apr 10, 2026

Choose a reason for hiding this comment

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

Peer dependency conflict with eslint-plugin-react-hooks upgrade

Medium Severity

Upgrading eslint to ^10.0.0 creates an unmet peer dependency with eslint-plugin-react-hooks at ^7.0.1. The latest stable version (7.0.1) declares its peer dependency as eslint ^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9, which does not include ^10. ESLint v10 support was added only in unreleased canary builds of 7.1.0. This will cause npm install to fail or warn depending on npm's strict-peer-deps setting.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 71ef31e. Configure here.

"eslint-plugin-react-hooks": "^7.0.1",
"eslint-plugin-react-refresh": "^0.5.0",
"globals": "^16.5.0",
Expand Down
Loading