* Update css-loader to 0.26.0

* Update the production webpack config

In the `create-react-app` command, try to install packages using Yarn.
If Yarn is not installed, use npm instead.

In `react-scripts`, detect if the project is using Yarn by checking if
a `yarn.lock` file exists. If the project is using Yarn, display all
the instructions with Yarn commands and use Yarn to install packages
in `init` and `eject` scripts.

* Correctly checks site url to tab url in reuse check

* Bring chrome to foreground focused after tab reuse

* Update `babel-plugin-transform-object-rest-spread` to v6.19.0

The `babel-plugin-transform-object-rest-spread` v6.19.0 update will
allow us to remove the `babel-plugin-transform-es2015-destructuring` and
`babel-plugin-transform-es2015-parameters` as the object rest spread
transform will now work standalone and not require additional tranforms

* Remove unnecessary babel transform plugins from babel-preset-react-app

The `babel-plugin-transform-object-rest-spread` v6.19.0 update makes
these plugins unnecessary, as v6.19.0 can be used stand-alone

Explain the usage of react-jsx-source & react-jsx-self

* Update babel-preset-env to 0.0.8

Changes between 0.0.6 and 0.0.8 should be backwards compatible:
https://github.com/babel/babel-preset-env/blob/master/CHANGELOG.md

* Use `node: 'current'` as target for babel-preset-env

This replaces the hand-rolled node version setup with a new feature that
was introduced in babel-preset-env@v0.0.7

https://github.com/babel/babel-preset-env/blob/v0.0.7/CHANGELOG.md

* Allow webpack 2 as peerDependency

* Remove webpack as peer dependency

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.

* Always build before deploying to gh-pages

* Add line to gh-pages deploy docs about CNAME file

* Remove spaces in npm run command for Windows

* Grammar nit

* Minor tweaks

Running `create-react-app` in a Docker container causes an unhandled rejection error in nodejs > 6.5 because the `opn` module tries to open a web browser in a system that doesn't have one. I figured this error could be safely ignored.

gh-pages supports https. It's important for prominent help files to encourage best practices.

 - 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

This reverts commit 1ef6ea52.

Enable no-webpack-loader-syntax rule in eslint-config-react-app.

* 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.

* Enable babel parameters/destructuring for all versions of Node

* Add more descriptive comment explaining plugin use

* Added note about env server restart

As discussed in [#870](https://github.com/facebookincubator/create-react-app/issues/870)

* Style nit

Running tests with the `-u` flag is a more reliable way to upgrade,
because the watch mode only runs tests for changed files.

* Add supports for prelease tags version

* Add comment to regex

* Cut everything after the first -\d

* Make semver version optional, so just package name get parsed correctly

* 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