* use safer/more aesthetic syntax

* fix typo

The launch configuration code provided is not compatible with VSCode since version 1.19.
The proposed documentation change is based on the response by a VSCode team member.

References:
https://github.com/facebookincubator/create-react-app/issues/3602#issuecomment-352075571
https://github.com/Microsoft/vscode/issues/40293#issuecomment-352017028

Replaced `it's` with `its`

the code got updated from `detect()` to `choosePort` while the comment did not.

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))

Fix another dead link

* docs: adding section about debugging tests

* docs: removing node-inspector references

* docs: replacing terminal command with npm script

* Update README.md

* add —use-npm flag to bypass yarn

* add e2e test for —use-npm flag

* improve eject message

* cross os implementation

* extra watch options regex to react-dev-utils

* fix regex

* add test

* fix eslint error

* include react-dev-utils test in CI script

* attempt to fix import error

* attempt to fix error on CI

* Update .eslintrc

 - react-scripts@1.0.17

"subway" by itself is not a proper noun

* Add link to VS Code troubleshooting guide

* Update README.md

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

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

* 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