TL;DR Arrow functions are fine for certain usages, but they have so many variations that they need to be carefully controlled to not break down the readability of the code. While arrow functions clearly have a ubiquitous community consensus (though not unanimous support!), it turns out there’s a wide variety of opinions on what makes “good” usage of => and not. Configurable linter rules are the best solution to wrangling the variety and disagreement of arrow functions. I released proper-arrows ESLint plugin with several configurable…