Update ESLint config

[DABH]

No description provided.

[wbt]

Any particular reason for this change?
Though your fork may be up-to-date as of the pull request, it seems likely to quickly fall behind, possibly producing some dependency issues as seen elsewhere, and we won't know why this change was made to make an informed decision about switching back. There may be good reason for the switch, but please document that reason here before merging.
Thanks for all your contributions!

[DABH]

@wbt The intent is (1) to use the same lint rules etc. we’ve already been using, but (2) to have a copy of the config rules that we can maintain (I can merge PRs for dependabot alerts for example). Not a huge deal since this is only for dev dependencies, but still nice to have a solution that — for now — guards against dependency rot

[DABH]

(There is no reason to switch back since the previous fork is not maintained, but if I ever disappear, you may want to switch to a standard config and just deal with reformatting the repos according to some different rule sets. Or fork my fork and update again.)

[wbt]

Did you ask @indexzero about possibly getting commit rights in that repo, if he's not maintaining it anymore?
Then the fixes could benefit the whole subset of the npm ecosystem that uses it.

[DABH]

I don’t remember, but I think we were approximately the only folks using that repo

[wbt]

My fuzzy memory is that it was one of the options presented in eslint-init, which could mean more. npm reports 1474 weekly downloads, which isn't much but I think is more than can be accounted for by Winston maintainers.