Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -265,7 +265,7 @@
"eslint-plugin-no-relative-import-paths": "^1.6.1",
"eslint-plugin-react": "7.37.5",
"eslint-plugin-react-hooks": "6.1.0",
"eslint-plugin-react-you-might-not-need-an-effect": "0.5.3",
"eslint-plugin-react-you-might-not-need-an-effect": "0.10.0",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Removed rule reference will break ESLint execution

High Severity

Bumping eslint-plugin-react-you-might-not-need-an-effect to 0.10.0 removes the no-empty-effect rule (per the release notes' breaking changes), but eslint.config.ts still configures react-you-might-not-need-an-effect/no-empty-effect at line 941. ESLint throws an error when a configured rule doesn't exist in its plugin, even when set to 'off', so this will cause all ESLint runs to fail.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit d5fdd66. Configure here.

"eslint-plugin-regexp": "^3.0.0",
"eslint-plugin-testing-library": "^7.16.0",
"eslint-plugin-typescript-sort-keys": "^3.3.0",
Expand Down
127 changes: 81 additions & 46 deletions pnpm-lock.yaml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading