This are four tools work in the same basic way. They are use to analyze and report problems in JavaScript and helpful in debugging JavaScript.
| JSLint | JSHint | JSCS | ESLint |
|---|---|---|---|
| It's oldest. The downsides are that JSLint is not configurable or extensible. You can’t disable many features at all. | JSHint was created as a more configurable version of JSLint (of which it is a fork). | JSCS is a code style checker. This means it only catches issues related to code formatting, and not potential bugs or errors. | ESLint is the most recent out of the four. It was designed to be easily extensible, comes with a large number of custom rules, and it’s easy to install more in the form of plugins. |
My choice of these four is ESLint. Because it support ES6.
A linting tool is a good step towards catching problems, but it only sees as many errors as its rules permit. For a more foolproof automated bug-catcher, I recommend using unit tests. Code reviews can also be useful for this purpose.
How do you and your team ensure the quality of your code?
No comments:
Post a Comment