UPDATE: The syntax is now supported by the latest versions of @typescript-eslint/parser and @typescript-eslint/eslint-plugin. ESLint support for TS import type syntax is working in progress. Issue: https://github.com/typescript-eslint/typescript-eslint/issues/1436 Pull request: https://github.com/typescript-eslint/typescript-eslint/pull/1465
Usually you don’t want to disable the rule. However, there are few cases where it’s worthwhile to disable it. For example, if you’re doing a fetch on mount and you’re sure it never has to execute again, you can disable it with the code below. // eslint-disable-next-line react-hooks/exhaustive-deps First, confirm the rule is wrong. It … Read more
I also encountered the same problem, I solved the problem by removing the project property under parserOptions parserOptions: { ecmaFeatures: { jsx: true, }, ecmaVersion: 12, sourceType: ‘module’, // project: ‘tsconfig.json’, tsconfigRootDir: __dirname, },
This seemed to do the trick for me. npm install -D eslint-import-resolver-typescript I don’t want to delete package-lock.json because I know from experience that doing so causes problems for my current project.
I did this and it work just fine for me “@typescript-eslint/eslint-plugin”: “^5.0.0”, “@typescript-eslint/parser”: “^5.0.0”, “eslint”: “^8.1.0”, Update those three packages Then run in the root of your project this command to update the packages npm i And it will work fine
You can disable this verification for rest siblings adding “@typescript-eslint/no-unused-vars”: [“error”, { “ignoreRestSiblings”: true }] to your list of rules in eslintrc.js. Example: module.exports = { root: true, parser: “@typescript-eslint/parser”, plugins: [ “@typescript-eslint”, ], extends: [ “plugin:@typescript-eslint/eslint-recommended”, “plugin:@typescript-eslint/recommended” ], rules: { “@typescript-eslint/no-unused-vars”: [“error”, { “ignoreRestSiblings”: true }] }, settings: { react: { version: “detect” } … Read more
Source: I am the maintainer of the typescript-eslint project. The latest version of the @typescript-eslint tooling now has full support for scope analysis. So the steps to fix this are now: update your versions to at least v4.9.1 of @typescript-eslint/parser and @typescript-eslint/eslint-plugin update your ESLint version to at least v6.0.0 update your config to use … Read more
Source: I am the maintainer of the typescript-eslint project. If you update your versions of @typescript-eslint/parser and @typescript-eslint/eslint-plugin to v4.1.0, you will be able to use the latest changes which make @typescript-eslint/no-unused-vars work properly for all cases. As an aside – using v3.x of the plugin but v4.x of the parser will put you into … Read more
Only way that I found is to use ignore pattern argsIgnorePattern in rule options. If your variable is unused, just add underscore _ctx and ESLint will ignore it, but no-unused-vars rule will still work for other values. After you will need to use this value, just remove underscore ctx. // note you must disable the … Read more
add this to the .eslintrc (tslintrc) file : rules: { “@typescript-eslint/no-explicit-any”: “off” },