- babel-preset-react-app@2.0.1
 - eslint-config-react-app@0.5.0
 - react-dev-utils@0.4.1
 - react-scripts@0.8.2

* Add Subresource Integrity support

* Pin dependency

 - react-scripts@0.8.1

 - babel-preset-react-app@2.0.0
 - create-react-app@0.7.0
 - eslint-config-react-app@0.4.0
 - react-dev-utils@0.4.0
 - react-scripts@0.8.0

* Replace `scriptPreprocessor` config with `transform`.
* Also remove `moduleFileExtensions` which has been redundant since 16.0
  (`['js', 'json', 'jsx', 'node’]` is the default)

* Remove bundledDependencies
* Change the e2e scripts to use local file dependencies instead of
  bundledDependencies to test the packages

* Update css-loader to 0.26.0

* Update the production webpack config

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.

 - babel-preset-react-app@1.0.0
 - create-react-app@0.6.0
 - eslint-config-react-app@0.3.0
 - react-dev-utils@0.3.0
 - react-scripts@0.7.0

* 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

* Update react-scripts dependencies to use jest 16

* Remove testRegex from Jest config (now default)

 - react-dev-utils@0.2.1
 - react-scripts@0.6.1

Removes a deprecation warning:
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue

See: https://github.com/jergason/recursive-readdir/pull/39

 - babel-preset-react-app@0.2.1
 - create-react-app@0.5.0
 - eslint-config-react-app@0.2.1
 - react-dev-utils@0.1.0
 - react-scripts@0.5.0

* Extract some utilities into a separate package

* Add utils dir to `files` in package.json

* Do not create an empty `utils` dir on eject

* Load environment file via dotenv if .env file is present

* Document loading environment variables in .env file

* Minor doc tweaks

Fixes #410, #674

* Update eslint-plugin-react and enable new rules

New rules:
* `react/no-danger-with-children` (yannickcr/eslint-plugin-react#710)
* `react/no-find-dom-node` (yannickcr/eslint-plugin-react#678)
* `react/style-prop-object` (yannickcr/eslint-plugin-react#715)

* Remove react/no-find-dom-node for now

* Move ESLint configuration to a separate package

* Remove the ESLint configuration, moved to eslint-config-react-app

* Update ESLint instructions

* Pin the package versions in eslint-config-react-app

* Add a README for eslint-config-react-app

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update package.json

* Update package.json

* Update production eslint-loader config

* Add the ESLint config to devDependencies of the repo

* Revert "Add ES5 version of `path-exists` to CLI"

This reverts commit fc3ab46d.

* Use pre node@4 compatible `path-exists`

Ref #617