[EXPERIMENTAL] Run standard --fix

[rreusser]

This is a test PR, mainly to get the ball rolling and see what would happen if we simply applied standard formatting. There are lots of rules that will require manual rewriting.

In particular, the vast majority look like

convert.js:219:72: ':' should be placed at the beginning of the line.
index.js:34:3: Split initialized 'var' declarations into multiple statements.

It's probably a couple hour pass to go through and fix those, then a bit more work to figure out maybe a few more subtle issues.

See: #950 ping @etpinard

[etpinard]

Hey, at least all the ; are gone!

[rreusser]

Of note:eslint is the only phase of the tests this PR broke (which is not a foregone conclusion considering 408 files +41,098 / −42,357)

[rreusser]

Common sentiment overheard: "OMG eslint is just horrible to have to run all the time. prettier solves this whole problem in a way that makes fundamentally so much more sense. So over eslint." Paraphrasing, of course. People seem very excited about dumping eslint for prettier though. In summary, eslint 'fixes' your code by tweaking it. Prettier parses the AST, dumps the original code, and reprints it with perfectly consistent and standardized formatting.

If I understand then, there aren't rules to violate. You write code. It reinterprets it and applies its own formatting. Seems nice.

[rreusser]

Holding off until some large PRs have been merged.

[rreusser]

FWIW:

[rreusser]

Closing for now. Can revisit if changing the linting seems like the right move.