* Don't ask to install webpack for using Styleguidist

* Update README.md

* Put react-scripts in dependencies, not devDependencies

* Sort dependencies on eject

* Remove CI check

Adding the word "also" to "Can you also reproduce the problem with npm 4.x?" clarifies that contributors aren't _expected_ to use NPM v4, but we're interested in understanding which environments the reported issue affects.

* adding comment on windows support of nvm

* adding tree structure for intial project output

* applying feedback from this thread create-react-app/pull/1931

* Added instruction on how to install Prettier

* Tweak style

* Update README.md

* Update README.md

* Support JSX

* Update README.md

* Update README.md

I know this is a very minor thing, but correct grammar makes it easier to understand.

In the section about npm run build fails in troubleshooting added more
info about memory usage of the build script and a link to a tutorial for
adding more swap space as a viable solution.

* Update docs with WebSocket proxy information

* Tweak wording

Due to many of the other examples in the README showing both `npm` and `yarn` commands.
I have added an example of how to install a dependency using `yarn`.

* Add service worker invalidation

* Update valid service worker check only on local host

* Fix sourcemap directory organizing on Windows

* Update comments

* docs: added REACT_EDITOR to `Advanced Configuration` section

* Update README.md

* Update launchEditor.js

* Auto-detect running editor on Windows for error overlay

* Ignore process output if powershell call fails

* Support Notepad++

* Local testing with docker

* Docs on e2e testing

* `bash` callback after docker

* Add a TL;DR in the CONTRIBUTING section

* Local e2e testing with modified files

* Remove the N.B. from the README

* Fixed a fixme in e2e doc

* add docs for setting up CircleCI for CRA

* Reword

Since `v2.2.1` of webpack the need for `ident` for complex options is no longer required. See

https://webpack.js.org/guides/migrating/#complex-options

* Update sw-precache-webpack-plugin to v0.11.3

* Pin the version

* Adding link to tutorial on code splitting

Link to tutorial on Code Splitting with React Router

* Update README.md

https://www.jetbrains.com/help/webstorm/opening-files-from-command-line.html
https://www.jetbrains.com/help/phpstorm/opening-files-from-command-line.html

Both editors have the same signature `<editor> <projectPath> --line <number> <filePath>` to open file from the command line.
It seems to work even if `<projectPath>` is omitted (commit 02f88ba1).

Tested on `Win10`+`PhpStorm2016` and `macOS 10.12`+`PhpStorm2017`.

* New issue template

* Update PULL_REQUEST_TEMPLATE.md

* Update ISSUE_TEMPLATE.md