* Update dependencies in react-scripts

* Add first pass of working dependencies for babel-preset-react-app and react-scripts

* Bump more dependency versions

* Adjust more versions and edit fix options

* Restore functionality of old preset

* Disable Uglify in iframe webpack

* Apply prettier

* Re-enable cache in dev and clean deps

* Lock packages and move babel/core to dep in preset

* Bump babel-jest

* Re-enable uglify

* Nest forceAllTransforms correctly in webpack config

* Install babel-core bridge for jest

* Add jest-cli and babel-core bridge to make tests in react-error-overlay pass

* Re-enable transform-dynamic-import

* Add dynamic import syntax support back

* Use new babel in kitchensink

* Transform modules in test

* Revert "Transform modules in test"

This reverts commit 539e46a1.

* Attempt fix for ejected tests

* try this

* Add regenerator back

* Bump babel deps to beta.34

...

 - babel-preset-react-app@3.1.1
 - create-react-app@1.5.0
 - eslint-config-react-app@2.1.0
 - react-dev-utils@5.0.0
 - react-error-overlay@4.0.0
 - react-scripts@1.1.0

Fixes #2793

This fixes the broken link to removed `href-no-hash.md` file, that is no longer available in the [eslint-plugin-jsx-a11y](https://github.com/evcohen/eslint-plugin-jsx-a11y) plugin (since [6.0.0](https://github.com/evcohen/eslint-plugin-jsx-a11y/blob/a14617528cda23c6c88902ace1d083e4e13ac271/CHANGELOG.md))

 - babel-preset-react-app@3.0.3
 - create-react-app@1.4.1
 - eslint-config-react-app@2.0.1
 - react-dev-utils@4.1.0
 - react-error-overlay@2.0.2
 - react-scripts@1.0.14

* File headers BSD+Patents -> MIT

* BSD+Patents -> MIT

The `npm install` script for outside usage instructions is outdated. Updated to match the package's current peer dependencies.

 - babel-preset-react-app@3.0.2
 - create-react-app@1.4.0
 - eslint-config-react-app@2.0.0
 - react-dev-utils@3.1.0
 - react-error-overlay@1.0.10
 - react-scripts@1.0.11

* Bump deps

* Fix linter errors

* Whoops

* Try to bump webpack

* Update peer deps to min for eslint 4.x

* Re-enable flowtype warning

* Update eslint-plugin-flowtype dependency

* Update eslint-loader 1.7.1 -> 1.9.0

* Add eslintPath option

* Update eslint 3.19.0 -> 4.1.1

* Update peer dependencies

* Move eslintPath config to outside @remove-on-eject

 - babel-preset-react-app@3.0.1
 - create-react-app@1.3.2
 - eslint-config-react-app@1.0.5
 - react-dev-utils@3.0.1
 - react-error-overlay@1.0.8
 - react-scripts@1.0.8

 - 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