In the Elm community, the closest equivalent is
elm-review, but that one has a lot less rules than ESLint (and not because I’m not writing them). That is somewhat understandable because we already have a compiler checking for some of those issues, and we have
elm-format to handle styling-related issues.
@supermario and I thought it would be really interesting to see how many of the ESLint rules applied in the Elm ecosystem. So I went through every single one of the 263 “core” ESLint rules (not from packages, there are so many that it’s not even funny to consider doing) and noted that down.
It was a bit hard to categorize everything (some things can fit into multiple categories), but I tried my best to be objective.
The results can be found below. Huge thanks to @supermario for editing the article and talking me into researching this. Note that some of the things are interactive