You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 12, 2025. It is now read-only.
This is required since the base rules report false positives in TypeScript (e.g. no-shadow reports enums) with the v4 typescript-eslint release (due to breaking changes in the scope analysis engine).
The no-shadow rule should be turned off and replaced with @typescript-eslint/no-shadow
The no-redeclare rule should be turned off and replaced with @typescript-eslint/no-redeclare
The text was updated successfully, but these errors were encountered:
I still had issues with this when using create react app. The issues went away after downgrading both this package and typescript. If this helps anyone out there getting stuck on this until every package is updated with the same workaround, it helped me to do the following:
First remove your node_modules. (rm -rf node_modules)
Then make sure your typescript is set to:
NOTE: this is not a fix. This is a workaround while waiting for react-scripts to release their fix. They are aware of the problem. If you want to track it, here is the issue: facebook/create-react-app#9515
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@typescript-eslint
v4 adds these new rules:This is required since the base rules report false positives in TypeScript (e.g.
no-shadow
reports enums) with the v4 typescript-eslint release (due to breaking changes in the scope analysis engine).no-shadow
rule should be turned off and replaced with@typescript-eslint/no-shadow
no-redeclare
rule should be turned off and replaced with@typescript-eslint/no-redeclare
The text was updated successfully, but these errors were encountered: