Previous changes caused `detect-port` to pick random port on app startup. Update fixes this regression, `detect-port` pick next available port instead.
* Whitelist files that can be embedded through url-loader
Change the current catch-all loader to use file-loader instead of
url-loader, and exclude common image file extensons. Add another url-loader
for images, configured identically to the original catch-all loader.
Part of issue #1293.
* Update tests to reflect change in loader config
* Integration test fix
* More CI fixes
* Work around broken loader-utils behaviour in integration tests
* Revise the documentation around file loading
* Documentation tweaks
* Docs tweak
* Update test now that webpack/loader-utils has been updated
* Update react-scripts to depend on babel-loader@7.0.0-alpha.2
* Bump deps
* Switch to preset-env
Disables webpack modules by enabling babel modules to resolve#1638
* Bump babel-core to match babel preset versions
* Add uglify to targets
* updating eslint to 3.16.1
* add support for ignoreRestSiblings in eslint
http://eslint.org/docs/rules/no-unused-vars#ignorerestsiblings
* updating eslint to 3.16.1 in `react-scripts`
* updating eslint
* missing `^`
* missing ^
* pinning main eslint and updating readme
* Pin ESLint version
* Replace `scriptPreprocessor` config with `transform`.
* Also remove `moduleFileExtensions` which has been redundant since 16.0
(`['js', 'json', 'jsx', 'node’]` is the default)
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.
* 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.
* 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
