Problem: If we allow ESLint warnings, the number of warnings will grow over time.

Here why:
🚫 It’s hard to see when new warnings occur
🚫 Noisy ESLint output makes us ignore it.

Solution: Run “eslint —max-warnings 0” on the CI server. Now any warning breaks the build. 👍

With max-warnings set to zero, the distinction between warnings and errors goes away. Either breaks the build. 👍

So, I typically set every enabled rule to a warning.

View original on X