I think formatters provide some value because they can make diffs much easier to read. If every developer on the team codes in their own style, diffs in PR's can be problematic because there are filled with brace changes, extra spaces between params, etc instead of just the functional code changes. Not to say that devs can't still create a lot of "false changes" even with a linter, but at least it's not 'cause curlies are on the same line or a different line.
Beyond just the formatting, lint does some useful things like suggest use of const instead of let, warn against reassignment of parameters, and some other sensible checks.
I do this we need to raise the bar significantly in terms of ease of use. Usually formatters are run as a pre-commit hook (or even on file save when IDE support is there). If we landed on either of those would you be receptive to continuing the use of such a tool?
I think Prettier is fundamentally better since it doesn't check your code for errors, it actually parses it and reformats it every time based on a set of a rules. So as long as your code is valid JS it should be fine, it will just get reformatted for you. So as a pre-commit hook, we shouldn't have to think about it at all. We just need to check to make sure there's some of those values checks in place too. (there is apparently a Prettier project that also supports some limited eslint integration)