* Add note for using CHOKIDAR_USEPOLLING in virtual machines to enable HMR

* Use br in react-scripts template README md

* Use br in md for new line breaks

* Update troubleshooting HMR to allow for VMs running Windows

* Fix up the instructions

 - babel-preset-react-app@2.1.0
 - create-react-app@1.0.4
 - eslint-config-react-app@0.5.1
 - react-dev-utils@0.5.0
 - react-scripts@0.9.0

 - 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

 - 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

Revert webpack prod config comments to not refer to dev server.

 - 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

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.

Now allows the use of short circuit and ternary expressions.

* 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