Can't override ESLint rule "@typescript-eslint/no-unused-vars"

I tried different possibilities to override the default warning setting for “@typescript-eslint/no-unused-vars”.

The config below is what I ended up with. I also added an additional rule “no-empty-function” just to see if the whole section gets interpreted which is the case. My goal was to disable the rule for test files like “**/*.test.ts?(x)” but neither works for me.

"eslintConfig": {
    "extends": [
      "react-app",
      "react-app/jest"
    ],
    "overrides": [
      {
        "files": [
          "**/*.ts?(x)"
        ],
        "rules": {
          "no-unused-vars": "off",
          "@typescript-eslint/no-unused-vars": [
            "off"
          ],
          "no-empty-function": 2
        }
      }
    ]
  },

Indeed, and that is interesting, it does work when I delete the lines from .\node_modules\eslint-config-react-app\index.js:82-88:

'@typescript-eslint/no-unused-vars': [
          'warn',
          {
            args: 'none',
            ignoreRestSiblings: true,
          },
        ],

After this hard patch I’m able to set the values “off”, “warn” or “error” in the package.json above as I wish and it works fine.

Having in mind that I upgraded to react-scripts 4.0.1 from an earlier 3x version.

[zallesov]

Non of the above solutions worked for me.

In my case the solution was to change the tsconfig.json

{
  "compilerOptions": {
    "module": "commonjs",
    "noImplicitReturns": false,
    "noUnusedLocals": false, // these were true
    .....

[fix-me]

I dont want to disable it for each of those thousands of test files manually with comments. Further these comments have the disadvantage to disable it. What do you do if you decide to warn about these errors or fail in production in future when passing quality gate?

There are reasons where you like to have these unused vars (momentary), for instance when you especially know that your code will evolve within the next sprints. You are able to prepare it as much as possible, so the next developer will catch up more easily, knowing what is important. Or you have some objects for debug purposes in the test files when you play around with them. It can be valid code though, so there is no need to comment the whole setup out.

I could find plenty of reasons, but for long story short: If I want unused vars, I want unused vars! 😉 I am talking about the technical impediment here, not about if it is useful or not.

Cheers!