--strict for counting warnings as errors

Soliciting feedback on the idea before doing the work. My apologies if this is already doable, but I didn’t find anything thus far…

Scenario

• Linting is ran before nodemon restarts, the build runs, etc.
• ESLint ensures that any syntax issues cause an error, preventing unnecessary server restarts, builds, etc.
• Warnings are available in the console for the developer to optionally clean up.
• Code works, builds run, servers restart, but there’s no way to actually enforce standards without making everything incorrectly an error.

Solution – --strict.

• A pre-push git hook can run eslint --strict and even warnings count as errors, preventing pushing.
• Continuous integration tools can run in strict mode so that the build breaks when quality tests don’t pass.
• The user can still work on a feature with warnings, since the most important thing is the feature working.

The gist is, quality should still be enforced somewhere in the process, but not be an impediment to development.

Thoughts?

[joshkel]

--max-warnings can serve this purpose: --max-warnings=0 means that any warnings cause eslint to report an error.

[michaelficarra]

Again, just don’t run the linter during development. Your one counterexample (syntax errors) can be solved by running a parser against the code as you write it, something many editors (including vim) will do for you.