* Add source-map-loader to support source maps of dependencies
* merge with latest develop
* add ModuleConcatenationPlugin
* revert source-map-loader
* bump to 3.1 and update dev-server
* rebase to master
* rebase again
* bump webpack
* remove ModuleConcatenationPlugin, downgraded react packages, bump etwp
* ETWP rc1 only for testing
* bump ETWP and webpack 3
* bump WP3
* revert to 3.2.0
* bump sw-precache-webpack-plugin
* bump back to 3.3.0
* bump dev-server and manifest
* Use oneOf to resolve correct loader
* Add html and json fallthrough again
* Use oneOf to resolve correct loader in dev
* Document file-loaders `js` exclusion
* Remove `jsx` from exclusion in prod config
Jest's default value for this option is ["js", "json", "jsx", "node"].
CRA's current value is ["web.js", "js", "json", "web.jsx", "jsx"], which
is missing one of default ones: "node". This change fixes that.
This "node" extension is used in packages that use native code.
* Add json and css to lint-staged in template README
This changes the proposed way about using prettier inside the README.md, because prettier supports css since the 1.4.0 release and json since the 1.5.0 release.
Was not sure if it was a good idea to add different regexes for json and css inside the README.md don't have a real opinion about it myself, could maybe easier for starters to do so if they wan't to add things like eslint or stylelint the the commit hooks.
* Use capitalization for Javascript, CSS and JSON
* Change 'Javascript to JavaScript'
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`.
* Local testing with docker
* Docs on e2e testing
* `bash` callback after docker
* Add a TL;DR in the CONTRIBUTING section
* Local e2e testing with modified files
* Remove the N.B. from the README
* Fixed a fixme in e2e doc
* Fix incorrect check if CI variable is set to true
Originally build would fail on warnings with any value of CI environment variable. Now it will correctly check if it's true.
Discussed here: https://github.com/facebookincubator/create-react-app/issues/2453
* Check for "not false" instead of "not true"
After discussion we decided that this will be closer to current functionality and not break anything.
