Upgrade `babel-loader` and remove the cache directory configuration
that was added in #620. `babel-loader` now uses the
`./node_modules/.cache/babel-loader` directory by default, so the
custom config is no longer needed.
* Always build before deploying to gh-pages
* Add line to gh-pages deploy docs about CNAME file
* Remove spaces in npm run command for Windows
* Grammar nit
* Minor tweaks
Running `create-react-app` in a Docker container causes an unhandled rejection error in nodejs > 6.5 because the `opn` module tries to open a web browser in a system that doesn't have one. I figured this error could be safely ignored.
* Update dependencies
* Use published version of eslint-config-react-app for development
We dogfood on our eslint-config-react-app by using it as our ESLint config,
but installing it from the local folder causes problems when its peerDependencies
are updated, because npm won't update it unless the version number changes.
Use the published version for dogfooding so it can be installed from npm.
* Add supports for prelease tags version
* Add comment to regex
* Cut everything after the first -\d
* Make semver version optional, so just package name get parsed correctly
* Create asset filenames mapping on the build output
I use danethurber/webpack-manifest-plugin on Webpack production
configuration to create a file named `asset-manifest.json` which contain a
mapping of all asset filenames to their corresponding output file.
`asset-manifest.json` will be located at the root of output folder.
This'll resolve#600
* Add an explanation for ManifestPlugin
* Make webpack-manifest-plugin's version exact
* Support passing scoped package names to --scripts-version arg
* Factor out bitwise operator in indexOf test
* Comment on stripping only version or tag from package name arg
* Disable ES2015 transforms based on node version using babel-preset-env
* pass major version number for node to babel-preset-env instead of version string
* use parseFloat() instead of parseInt() to parse node version
* fixed style nits
A previous commit renamed the apple script to open chrome from
`chrome.applescript` to `openChrome.applescript`. That created
a minor bug. Even when chrome was open with the client app,
`npm start` would open the client app in a new Safari tab on
macOS instead of re-using the open tab in chrome.
