ericcornelissen/js-regex-security-scanner

Avoid outputting errors/warnings due to references to unknown ESLint rules

Closed this issue · 0 comments

ericcornelissen commented

When a project uses ESLint itself and has in-code eslint-ignore-* comments, running this project on it results in errors/warnings about unknown rules. For example:

[...]

/project/path/to/some/file.js
  2:1  error  Definition for rule '@typescript-eslint/no-explicit-any' was not found  @typescript-eslint/no-explicit-any

[...]

This is not ideal because it introduces noise and makes the exit code (ref #3) useless.