npmtypescript95% confidence\u2191 90

How to bypass warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any

Full error message

We have a strict zero lint issues policy. This means all errors and warnings need to be fixed.

Facing this lint error in our React typescript project:

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

Tried this: // eslint:@typescript-eslint/no-explicit-any: "off" which is not working.

How can I bypass this rule?

Solutionsource: stackoverflow \u2197

In Angular we add that in the TypeScript rules. Not in the general rules because sometimes that doesn't work. Example: "rules": { "@typescript-eslint/no-explicit-any": ["off"] } In the .eslintrc.json file

API access

Get this solution programmatically \u2014 free, no authentication.

curl https://depscope.dev/api/error/2bea7581eb5eaf909978ac26da86ae8f24a3f1da39c326e61c512034630ac6eb

hash \u00b7 2bea7581eb5eaf909978ac26da86ae8f24a3f1da39c326e61c512034630ac6eb