Format Code with Prettier and use Stricter Linter

[hipstersmoothie]

• Add prettier for consistent code formatting. Make contributing and reading the code a lot easier
  • took out editor config in favor of prettier
• Switch from eslint to XO. provides a far stricter linter and conforms better to modern JS practices.
• Add babel-preset-env to get ES features. I haven't actually modified the code to be to ESexy yet. That'll come in another PR

@edi9999 Would you like to review?

[edi9999]

I think in your changes, the files browser/lib/jimp.js should not be changed (they seem to be parsed by prettier/eslint)

[edi9999]

editorconfig still makes sense (it is used so that from any text editor, you already have the config well setup for that project).

[hipstersmoothie]

putting it back

[edi9999]

Why eslint-config-xo-react ?

[hipstersmoothie]

Oops. fixing this. moving babel dep all to dev as well

[hipstersmoothie]

this comment has been addressed

[hipstersmoothie]

@edi9999 hwo you you feel about me adding the browser/lib/*.js to the gitignore. It is really weird that the built versions of those files are committed. this would fix #433. I could set it up to only do it before a publish

[edi9999]

@edi9999 hwo you you feel about me adding the browser/lib/*.js to the gitignore. It is really weird that the built versions of those files are committed. this would fix #433. I could set it up to only do it before a publish

yes, +1 on this, I don't see why this would be commited each time.

[hipstersmoothie]

@edi9999 I'll exclude browser/lib/*.js in another PR. how does this one look now?

• I put back the editorconfig and reformatted
• Made prettier run on commit and ignore the built files for now
• Made sure all linting and testing passes

can you approve the changes?

[edi9999]

Thanks @hipstersmoothie !