* gh-1269: Enabling nested folder paths for project name

* gh-1269: Added "fs-extra" and removed "path-exists"

* gh-1269: Added e2e test cases to verify nested folder names

Browser launch can still be suppressed using BROWSER=none

* Adds note on how to resolve file or directory not found errors for heroku deployments

* Style tweaks

* Add "Changing the Page Title" to User Guide

* Add link to main README

Use a 'BROWSER' environment variable with npm start to specify which
browser to open. if the value of 'BROWSER' is not valid executable file,
don't open any browser.

 - create-react-app@1.0.2
 - react-dev-utils@0.4.2
 - react-scripts@0.8.4

* Tweak minimal Node error message

* Tweak console messages

* It doesn't need to be from npm

* Try to fix e2e test

* Use "commander" for  cli argv handling

* Handle different scripts version forms and exits without a name given

* Revert comment about min supported node version

* Check sooner for the minimal node version

* Add travis test for node <4

* Parse stderr in node versions <4

* Proxy rewrites Origin header to match the target server URL

* Added comments on rewriting Origin header by the proxy middleware

* Update CONTRIBUTING.md

* Add more detailed change log instructions

Previously create-react-app exited with 0 after an installation error.

* Remove the “‘yarn’ is not recognized as an internal or external
  command, ...” message on Windows
* Simplify the detection code: just run `yarn --version` – if it
  succeeds use `yarn`, if it fails use `npm`.

- Use “Chrome” instead of "Google Chrome", It  will try to use current active browser.
  otherwise, use default.
- If “Chrome”s aren’t running, will fallback to opn(url)

 - create-react-app@1.0.1
 - react-scripts@0.8.3

* Catch synchronous errors from spawning yarn

* Fix issues

* Add syntax highlighting configuration guide.

* Update link.

 - 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