-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
[Bug]: "Do not use isMounted" linting errors after upgrading to latest eslint-plugin-react
(v7.36.0)
#3819
Comments
eslint-plugin-react
(v7.36.0)
eslint-plugin-react
(v7.36.0)eslint-plugin-react
(v7.36.0)
0a8092f#diff-a68b4df806433028f9365f075dfa2c89c1c0737f311412f95c6c5cd239001d58R42 Now we get an error with |
Yes, changing the I've submitted a PR that fixes this issue: #3821. |
See jsx-eslint/eslint-plugin-react#3819 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Chores** - Updated dependency management for `eslint-plugin-react` to ensure alignment with the latest stable releases. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Minimal reproduction for anyone interested:
Confirmed in ( |
Thanks; #3821 already has a test case, and will be landed and released soon. |
I was going crazy, happy to see this was reported. |
Hey, v7.36.1 should be tagged as latest. |
It is (as is every publish automatically/by default), and never wasn't. |
ah, thanks. fixed. |
Is there an existing issue for this?
Description Overview
Before upgrading from v7.35.2 to v7.36.0, my linting tests were running with no errors, now they throw 4 errors about the usage of isMounted
npm run lint
output:We are not using isMounted in our codebase
full command used:
npm run rm && npm i --dev && npm run build && npm run lint
I later pinned the version back to v7.35.2 and the errors were no longer present
Expected Behavior
Before the upgrade:
eslint-plugin-react version
v7.36.0
eslint version
v8.57.0
node version
v16.20.2
The text was updated successfully, but these errors were encountered: