ESLint should report *ZERO* warnings or errors on CI
ESLint should report *ZERO* warnings or errors on CI. If one occurs, it should break the build.
If warnings/errors are ignored, then ESLint becomes useless overhead. It's just noise.
The solution?
1. Disable rules until no warnings/errors occur.
2. Add rules back over time.
You can enforce no warnings on CI via a command line flag:
--max-warnings
https://eslint.org/docs/latest/user-guide/command-line-interface#--max-warnings