* Uncomment merged PRs
* Switch to br
* Update some webpack links
* Add a little about section for PWA
* oops
* fast on subsequent visits
* Add manual proxy config instructions
* hint package.json
* Change to js for comments
* Tune wording
* sw-precache-webpack-plugin, SW registration, manifest.json
* Documentation + a few SW tweaks.
* Added an unregister method, too, just in case.
* More info for the READMEs.
* Add minify to SWPrecacheWebpackPlugin config
* Fix SWPrecacheWebpackPlugin typo
* Fix file references in READMEmd
* Add instructions for testing service-worker locally
* Review feedback
* Some additional PWA metadata
* Use sw-precache-webpack-plugin v0.9.1 for node >=4.0.0 support
* Review feedback.
* Add manifest.json context in a comment.
* Fix typo
* Downgrade to sw-precache-webpack-plugin 0.9.1
* Hide changes in README until 1.0
* Hide changes in User Guide until 1.0
* Hide more docs
* Override Jest config collectCoverageFrom with package.json
* Protect against overriding other options
* Better error message
* Create Jest config early on eject
* Tweak wording
* Dry it up
* Only run tests in <rootDir>/src (#544)
* updates Jest to 19.0.2
* removes testPathIgnorePatterns from jest config
* adds testMatch to jest config to only match files in src
* Bump babel-jest to 19.0.0 to match jest 19.0.2
* Adding postcss-flexbugs-fixes
Using postcss-flexbugs-fixes to fix all flexbug's issues.
* Adding flexbox: 'no-2009' to Autoprefixer
It will add flexbox prefixes only for final and IE versions of
specification.
* Support node scripts in BROWSER
Modify OpenBrowser.js to run node scripts specified with the BROWSER environment
variable . If the value of the BROWSER environment variable ends with '.js' a
child process is spawned to execute the script with node.js. Any
arguments passed to npm start are also passed to this script, as well as
the url where the app is served.
The command executed in the child process is:
node <pathToScript> [OPTIONS] <url>
Update User Guide.
* Tweak code style
* Pin dep
* Comment out 0.10 docs
* Support hoisting react-scripts
* require.resolve() loaders and configs
This makes it so that loaders and configs are resolved relative to the config rather than to the app. This seems to make more sense to me.
