Inline styles to fix style loading issues

[thomasjm]

This is meant to fix #121 .

The culprit was the styles in src/style/scss/global.scss, which required the use of style-loader, which doesn't work in SSR settings.

At first I tried switching it to isomorphic-style-loader, but that still felt too troublesome and heavyweight. It's such a small amount of styles that it was easiest to just inline them.

The main challenge was converting &:hover selectors to React state. I think I did this correctly, but if I missed any places it will manifest as some of the buttons appearing/not appearing when they're not supposed to with respect to hover. It would be good if someone familiar with this library could do npm run dev on this PR and click around to make sure everything still works the same.

I also upgraded a bunch of the dev dependencies like webpack. Note that css-loader/sass-loader/style-loader etc. are still present because they're used in the demo build. It would be good to inline things there too and get rid of all style loader stuff.

Thanks to @justinmchase for pinpointing the issue.

[justinmchase]

This looks excellent!

[correiamp]

@mac-s-g I've tested this PR and it works smoothly.
Do you have an ETA to go live?

[barvhaim]

waiting for this

[correiamp]

@usulpro @Kikobeats I've found in this thread that you're now contributors of this (amazing) project.
I really need this feature, could you please check if this PR can go live?

[pauljonescodes]

I'm sorry to pile in here, but I also would like this feature and have confirmed this branch works.

[paulshorey]

Confirmed. This PR works. The unit tests actually pass. I don't have time rn to get into this Travis CI test runner misconfiguration. Anybody know how to fix it?

Working example here: https://wordio.co
npm install git://github.com/paulshorey/rjv.git

I actually cloned the code from the latest commit in this PR, and installed it in my project. Built, committed, pushed to my own repo as a quick fix.

[mac-s-g]

testing now

[mac-s-g]

migrating discussion to #311 which contains commits to this repo. it's just making it easier for me to resolve the conflicts.

thank you to everyone contributing to the code and discussion.

[thomasjm]

Hooray, thanks @mac-s-g !

[correiamp]

Thank you @mac-s-g !

[correiamp]

@thomasjm, just to confirm, have you tested the new version with success?

I'm getting a strange problem with unit tests/code coverage and I want to confirm if it's only happening to me.
When running unit tests/code coverage, it's showing the local path of this project, like the image shows:

I've tried to remove it from coverage in jest.config but without success.
Do you have the same problem?