* Allow importing package.json
* Remove package.json import from App.js template
* fix importing package.json
* Rename variable to reflect path is relative to root
* Check for both package & package.json in ModuleScopePlugin
* Use regex to check relative path to package.json
* Strictly enforce package.json extension on scope plugin
* Add allowedPaths to ModuleScopePlugin ctor and use it to allow app package.json
* Remove package.json import from App.js template
* Add package.json to react-scripts/template, show package version and name in the template
* Remove import package.json from template
* Remove template/package.json and its references in code
* Update ModuleScopePlugin.js
* Update README.md
* format UglifyJs error
* move formatBuildError to react-dev-utils
* fix readme
* use regex for plucking the path from stack
* make path human readable and fallback to show error if regex not matched
* rename to printBuildError and add link to the docs
* fix link indentation
* improve readibility + shorten link
* 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`.
