Upgrade to Babel 7

[chapati23]

Description

This PR updates the setup to babel 7 (@^7.0.0-beta.40, to be precise). The one thing I noticed is that on the "Admin" page there are two alerts for some reason. Couldn't get to the bottom of that unfortunately.

While updating to babel7 I noticed that the precommit hook was failing due to conflicting eslint and prettier rules. Also, some of the eslint plugins you installed as dependencies appeared to never have been in effect, actually (eslint-plugin-react e.g.). I've installed eslint-plugin-prettier along with eslint-config-prettier to leverage prettier for what it does best (formatting) and eslint what it does best (linting). I realize code formatting is a highly personal subject so let me know if any of the stylistic changes resulting from leveraging prettier more are making your inner code fashionista itchy. Happy to work around your preference. But since I moved to just letting prettier do the formatting work, I've never looked back :)

Done

• Updated setup to babel 7
• Updated all npm packages to latest version
• Married prettier and eslint so they don't step on each other's toes anymore
• Fixed a shit ton of eslint errors so that the precommit hook is actually useful again (some warnings remain, tho)

How to test

Dev Mode

1. Check out this branch
2. Run yarn
3. Run yarn start
4. Click around and see that everything still works

Prod Mode

1. Check out this branch
2. Run yarn
3. Run yarn start:prod
4. Click around and see that everything still works

[faceyspacey]

This one unfortunately is rougher, as I'm about to release Rudy, and there are changes to the demo/boilerplate based on that. I'm tempted to just take what you've done here and apply it there, as any time working on this puts Rudy back even farther. I pretty much agree with all your findings, and really appreciate this!

[chapati23]

Yeah, the babel-related stuff should be pretty much interchangeable elsewhere. The eslint/prettier stuff: up to you.

…

Sent from my iPhone

On Feb 19, 2018, at 18:58, James Gillmore ***@***.***> wrote: This one unfortunately is rougher, as I'm about to release Rudy, and there are changes to the demo/boilerplate based on that. I'm tempted to just take what you've done here and apply it there, as any time working on this puts Rudy back even farther. I pretty much agree with all your findings, and really appreciate this! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.