In the section about npm run build fails in troubleshooting added more
info about memory usage of the build script and a link to a tutorial for
adding more swap space as a viable solution.
Due to many of the other examples in the README showing both `npm` and `yarn` commands.
I have added an example of how to install a dependency using `yarn`.
Simplified steps for deploying app to `now` as a static site. No need to `serve` script in `package.json` file. As of May 15, 2017, all static deployments on `now` are free and unlimited.
* 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
* 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 different env configs.
* fomrat code
* Hide doc
* Slightly rework the PR
* Remove .env in default template
* Use just one entry in the paths
* Unify env.js and loadEnv.js
* Oops, forgot these folks
* update readme with fix from https://github.com/facebookincubator/create-react-app/issues/1939
* update with better globbing
* added note
* updating with a note and reverting previous changes
* how about this?
* refactor
* added note about new files back in after verifying locally
* spaces back in, sorry was my editor!
* removed note about new files :)
* added bullet about new files issue currently open on node-sass
* resolvesfacebookincubator/create-react-app#1986 updates CSS Preprocessor docs to include information on node-sass-chokidar alternative to node-sass
* Update README.md
* Node.js serving with absolute path
It’s safer to use the absolute path of the directory that you want to serve, in case you run the express app from another directory.
* Update README.md