* 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

* Fix incorrect check if CI variable is set to true

Originally build would fail on warnings with any value of CI environment variable. Now it will correctly check if it's true.

Discussed here: https://github.com/facebookincubator/create-react-app/issues/2453

* Check for "not false" instead of "not true"

After discussion we decided that this will be closer to current functionality and not break anything.

It should be `baz` instead of `bar` on last example.

* Update README.md

Fix broken link to React Router documentation

* Update README.md

This eliminates a `yarn` warning on OSX machines running Node.js 8. See
here for details: https://github.com/strongloop/fsevents/issues/170

You can see an example of the warning in the second screenshot in
https://github.com/facebookincubator/create-react-app/issues/2422#issuecomment-305218252

- Call `npm run flow --init` won't create a .flowconfig file, it should be `npm run flow init`

* Update README.md to make links to webpack point to webpack.js.org instead
  insteade of webpack 1 webpack.githup.io

Resolves #2481

* Added NamedModulesPlugin in webpack.config.dev.js

* Update webpack.config.dev.js

* re-add storybook && update the documentation and links

* Change to new documentation domain

Removed Node v4 (CRA only supports Node >= 6)

"ensuring that you web app" ->
"ensuring that your web app"

since CRA now use the latest version of Jest under the hood,
`jest-enzyme` v3.2.0 is now working perfectly fine

* Fix detection of parent directory

* Correct parent directory detection fix

Add windows specific path and extend to issuer path

* Added cache clear to e2e scripts

* Install latest yarn on AppVeyor to avoid windows crashing bug in yarn

* Alternative fix for yarn crashing e2e tests on windows machines

* Revert "Fix wrong path expansion in end-to-end test (#2388)"

This reverts commit 2aafaad7.

* Revert "Suggest just "yarn build" (#2385)"

This reverts commit 70bf1250.

* Revert "Catch "No tests found" during CI (#2387)"

This reverts commit 5317b3f9.