- eslint-config-react-app@1.0.4
 - react-dev-utils@2.0.1
 - react-error-overlay@1.0.6
 - react-scripts@1.0.6

* Upgraded eslint-plugin-jsx-a11y to 5.0.3 to take advantage of
  d70ac7d7975819e7a52b85465ec67a0d93eb962a

 - eslint-config-react-app@1.0.3
 - react-dev-utils@2.0.0
 - react-error-overlay@1.0.5
 - react-scripts@1.0.5

 - eslint-config-react-app@1.0.2
 - react-dev-utils@1.0.3
 - react-error-overlay@1.0.3
 - react-scripts@1.0.3

Until this issue (https://github.com/gajus/eslint-plugin-flowtype/issues/165) is
fixed we're disabling `flowtype/require-valid-file-annotation`.

 - eslint-config-react-app@1.0.1
 - react-dev-utils@1.0.1
 - react-error-overlay@1.0.1
 - react-scripts@1.0.1

* Add documentation about using code splitting

* Revise docs a bit

* Update README.md

* Update README.md

* Update README.md

* Bump dependencies

* Bump CSS deps

* Somehow I missed dotenv

* Bump ESLint deps

* Tweak ESLint rules

Removing a stylistic lint rule

* ESLint Config: Upgrade eslint-plugin-jsx-a11y and activate more rules.

* Try to fix Lerna

* Update README.md

* Remove html-has-lang

* Update README.md

* Blacklist confusing global variables

* Blacklist globals

* Fix kitchensink test to lint

* Edit the list

* Use no-restricted globals for this

* Revert "Ignore the yarn cache directory (#2063)"

This reverts commit 94149c77.

* Revert "Forbid using window properties as global variables (#1840)"

This reverts commit 5a7d8e89.

* Forbid using window properties as global variables

* Change globals list to match Standard.

* Fix globals

Iterating over an object's keys using `for/in` is idiomatic and it's safe (in all modern browsers) to not check hasOwnProperty as long as the object is a plain object. Can we remove this lint rule?

* mv create-react-app/index.js -> create-react-app/creteReactApp.js

* update to modern code style

* var -> cosnt

* set trailing-coma to es5 for prettier

 - create-react-app@1.3.0
 - eslint-config-react-app@0.6.1
 - react-dev-utils@0.5.2
 - react-scripts@0.9.4

* Lint internal scripts with eslint:recommended

* Warnings r bad

* Bump jsx-a11y version

* Update package dependecy for jsx-a11y

* Bump version in react-scripts

* 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

 - babel-preset-react-app@2.1.1
 - create-react-app@1.1.0
 - eslint-config-react-app@0.5.2
 - react-dev-utils@0.5.1
 - react-scripts@0.9.1

* Disallow event global variable with no-restricted-globals rule (#1530)

* changed event global variable usage liniting from warn to error

* 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