fix #67 Redux reset appearance

[codekiln]

No description provided.

[codekiln]

The build issues for 2cd153a and 5bf49fb are with node-sass. One common solution is to add a postinstall key to the package.json which rebuilds node-sass. npm has an ability to rebuild just one package, but right now, it looks like the closest thing is yarn install --force, which rebuilds everything, and I'm not yet sure how to configure Travis CI to do that at the beginning.

I have seen a number of github issues raised because node-sass doesn't work with yarn: yarnpkg/yarn#1981 is one raised in the yarn repo.

I also see that it looks like it is using an old version of yarn on travis ci:

46.24s$ yarn
yarn install v0.17.8
[1/4] Resolving packages...

Yarn recommends installing yarn yourself if you override the install step in .travis.yml, but I am not.

Travis has more info on this:

• Install specific version of Yarn travis-ci/travis-ci#7471
• Upgrade preinstalled version of yarn travis-ci/travis-ci#7566

Downstream of that last issue was a notification that yarn will be upgraded in a coming 2017-09-06 update to the ubuntu trusty image: https://docs.travis-ci.com/user/build-environment-updates/2017-09-06/. After reading another recent blog post about the trusty rollout, realized that one can specify the distribution in the .travis.yml file

I'll try using dist: trusty, and see if that helps resolve the node-sass issue.

[codekiln]

It looks like until next week, sudo: required, group: edge is the only combination that works to load the latest yarn with the bugfix for node-sass's postinstall requirement. Unfortunately, as you can see in the Travis CI environment reference, the sudo: required image is a VM that requires 20-50s to boot, as compared with the sudo: false environment, which is container-based and only requires 1-6s to boot. When the new trusty environments are rolled out for container testing, I'll switch back to sudo: false for the faster build times.