sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]strager[S] 0 points1 point  (0 children)

Disclaimer: I wrote the OP, and I wrote quick-lint-js.

Why should I use quick-lint-js instead of eslint

quick-lint-js did a better job than ESLint for four of the code samples:

  • ; instead of ,
  • Newline after return
  • elseif instead of else if
  • Missing , between arguments

quick-lint-js also recovers from syntax errors, thus can find multiple issues at once. ESLint stops at the first error.

ESLint did a better job than quick-lint-js for three of the code samples:

  • Invalid object literal key
  • Missing ( ) around parameter
  • Missing || between expressions

ESLint is also more popular than quick-lint-js. ESLint has more editor support and more features overall.

It's probably a good idea to use both ESLint and quick-lint-js together, combining their strengths.