Fixed a small grammatical issue that I noticed while browsing the README today

 - create-react-app@1.4.3
 - react-dev-utils@4.2.1
 - react-scripts@1.0.16

* Changelog for 1.0.15

* Update CHANGELOG.md

* Update CHANGELOG.md

Lerna is acting up.

 - babel-preset-react-app@3.1.0
 - react-dev-utils@4.2.0
 - react-error-overlay@3.0.0
 - react-scripts@1.0.15

* Add preflight CWD check for npm

* Typos

* Try a custom function

* fix path

* install rsync

* Test with node 8

* Ensure package is removed from the tree

* Remove ours

* matching functions

* try cygwin

* try c:/

* sigh

* Try /cygdrive/

* Try /cygdrive/

* Revert "Try /cygdrive/"

This reverts commit ab1ed779456d39bedbdb128a7aec3bb88b8eeb1c.

* Use sub-optimal copy

* Remove rsync install

* Fix variable

* Continue on err

* Don't link react-scripts, lol

* run yarn after eject

* re-enable cleanup

* uninstall yarn

* try with force

* appveyor ... seriously?

* swallow bad eject

* remove eject error swallow

* Revert "run yarn after eject"

This reverts commit eebf1dbc19aeb6e1f66d5ec27bda2d076bea0956.

* Run yarn after eject

* add a comment

* Change template manifest start_url to dot to make it react-router friendly

* Revert "Change template manifest start_url to dot to make it react-router friendly"

This reverts commit 02f53e81.

* Add a note about PWA manifest and client-side routing

instead of using `&&` to run multiple commands in `package.json`, guide users to use `npm-run-all`

According to this parameter's comment, it's unused but webpack-dev-server crashes without it. However, webpack-dev-server is running fine for me without this parameter.

This resolves #3272.

Implement settings as suggested here:
https://github.com/mishoo/UglifyJS2/tree/harmony#mangle-options

To solve this Safari bug:
https://bugs.webkit.org/show_bug.cgi?id=171041

Fixes #3284.

* Bump dependencies

* Downgrade source-map back to 0.5.x

Not sure what changed there but our bundle snapshot doesn't match with minor changes.
I couldn't figure out how to update it, and also whether we need to tweak getPrettyURL in response.

It's confusing: https://mobile.twitter.com/brianleroux/status/923581596720013312

h/t @brianleroux

* update eslint-plugin-react to 7.3.0

* Updated eslint-plugin-react to 7.4.0

The existing link lands on a 'this page has moved' placeholder that
doesn't redirect to the correct location. This PR replaces it with the
currently working URL.

Closes #3291

* Use production React version

* We cannot strip our own checks if production

* Keep the sourcemap during minify

* Prevent devtools pollution

* Add some comments

* sigh

* Add a warning when running minified

* Add more robust check

* Update index.js

* `react-error-overlay` has no dependencies now (it's bundled)

* Use babel 6 for now

* Implement click-to-open for babel syntax errors in build error overlay

* Add click-to-open support for lint errors and refactor parser

* Reactor code to reuse open-in-editor functionality in both build and runtime error overlays

* Fix some eslint warnings

* Add a comment about keeping middleware and dev client in sync

* Remove es6 features from webpack dev client

* Make open-in-editor functionality to work with new iframe script

* Rename `openInEditor` to `editorHandler`
 -  Remove indirection of openInEditorListener
 -  Check editorHandler for null before styling error clickable

* Fix flow errors