Disable typescript-eslint plugin rule (no-explicit-any) with inline comment

Question

I have an eslint error that comes from the @typescript-eslint plugin.

Unexpected any. Specify a different type.eslint(@typescript-eslint/no-explicit-any)

This is the no-implicit-any rule. In just one file I want to disable that rule with a comment at the top of the file.

The compiler complains if I just try a standard eslint disable:

/* eslint-disable  no-explicit-any */

Definition for rule 'no-explicit-any' was not found.eslint(no-explicit-any)

I've tried to find documentation on inline rules for the TS plugin, but without much luck. I've also tried various combinations like these:

/* typescript-eslint-disable no-implicit-any */
/* typescript-eslint: disable no-implicit-any */
/* typescript-eslint: disable noImplicitAny */
/* typescript-eslint-disable @typescript-eslint/no-implicit-any */

There are no eslint complaints but the error will not disappear.

How do I disable an typescript-eslint rule?

It would probably be good to update this question to read `no-explicit-any` every time, since you sometimes say `no-IMPLICIT-any`, even though that's a `tsconfig` option, not an ESLint rule. — Christian Jensen, Apr 20 '21 at 18:53

score 176 · Answer 1 · answered Mar 26 '20 at 13:31

176

add this to the .eslintrc (tslintrc) file :

rules: {
    "@typescript-eslint/no-explicit-any": "off"
  },

answered Mar 26 '20 at 13:31

abdelhedi hlel

2,903
1
16
20

21

The OP write "In just one file I want to disable that rule with a comment at the top of the file." – Marian Oct 12 '20 at 14:42
10

It is not OP request – nicoramirezdev Oct 16 '20 at 10:19
3

It might be necessary to restart the IDE – Washington Guedes Apr 23 '21 at 16:36
This has no effect in my project. Did something change? – HammerN'Songs May 24 '22 at 21:55

score 156 · Accepted Answer · answered Dec 02 '19 at 22:06

156

The correct syntax is like this:

/* eslint-disable  @typescript-eslint/no-explicit-any */

So that you directly reference the plugin via eslint.

answered Dec 02 '19 at 22:06

cham

8,666
9
48
69

4

This should be the accepted answer since it directly addresses OP's question about using at the top of the file, but other viewers here might want to note that unless you *really* want to disable linting for the entire file, you probably want to go with the [other answer](https://stackoverflow.com/a/66659083/758334). – Subfuzion Sep 19 '22 at 15:07

score 83 · Answer 3 · answered Mar 16 '21 at 16:12

83

If you're attempting to disable a rule on the next line only (rather than for an entire file), adding this comment directly above the line to ignore will work:

// eslint-disable-next-line  @typescript-eslint/no-explicit-any

answered Mar 16 '21 at 16:12

Meredith Murfin

841
4
4

You can also disable on the same line with e.g. ` // eslint-disable-line @typescript-eslint/no-explicit-any -- optional reason goes here` – ShadSterling Jan 18 '23 at 01:00

score 0 · Answer 4 · answered Jul 25 '23 at 12:44

0

You may also come across the following syntax, so you would update with value of 0 if it is set to 1:

'@typescript-eslint/no-explicit-any': 0,

answered Jul 25 '23 at 12:44

Abdush Samad Miah

186
1
8
19

Disable typescript-eslint plugin rule (no-explicit-any) with inline comment

4 Answers4