TK

I encountered the same problem

"@typescript-eslint" be declared as a peer dependency maybe is not a mistake. Because `[email protected]` use `@rushstack/eslint-patch/modern-module-resolution`. This patch allows a shared ESLint config to bring along its own plugins, rather...

`eslint-config-react-app` has already declared plugins with "@typescript-eslint", it is unnecessary declare again in your `.eslintrc.json` when you extend `eslint-config-react-app` Remove the duplicate "@typescript-eslint" from your `.eslintrc.json` could resolve `ESLint couldn't...

`plugins` declared as a `peerdependency` may not be a wrong. Because `[email protected]` use `@rushstack/eslint-patch/modern-module-resolution`. This patch allows a shared ESLint config to bring along its own plugins, rather than imposing...