Reputation: 11
{"files":["**/*.ts","**/*.tsx"],"parser":"@typescript-eslint/parser","parserOptions":{"ecmaVersion":2018,"sourceType":"module","ecmaFeatures":{"jsx":true},"warnOnUnsupportedTypeScriptVersion":true},"plugins":["@typescript-eslint"],"rules":{"default-case":"off","no-dupe-class-members":"off","@typescript-eslint/no-angle-bracket-type-assertion":"warn","no-array-constructor":"off","@typescript-eslint/no-array-constructor":"warn","@typescript-eslint/no-namespace":"error","no-unused-vars":"off","@typescript-eslint/no-unused-vars":["warn",{"args":"none","ignoreRestSiblings":true}],"no-useless-constructor":"off","@typescript-eslint/no-useless-constructor":"warn"}}
).Referenced from: D:{app folder}{app name}\package.json
Upvotes: 1
Views: 5433
Reputation: 131
I actually had this same issue when updating react-scripts
in my Create React App Project. My steps to resolve were.
package-lock.json
node_modules
eslint
dependencies from your devDependencies
in package.json
npm cache clear --force
npm install
npm install
the the latest versions of the eslint
packages you removed back to your devDependencies
This worked for me.
UPDATE: I actually did not need to install eslint after removing them when installing React Scripts 5. It seems to use it under the hood.
Upvotes: 1