The create-react-app need node >= 6, and node version 6 support a lot of ES6, and let's switch using '+' to concat string with template string.

Fixes #2883 

* bump wp3

* try bump babel-loader

* Add source-map-loader to support source maps of dependencies

* merge with latest develop

* add ModuleConcatenationPlugin

* revert source-map-loader

* bump to 3.1 and update dev-server

* rebase to master

* rebase again

* bump webpack

* remove ModuleConcatenationPlugin, downgraded react packages, bump etwp

* ETWP rc1 only for testing

* bump ETWP and webpack 3

* bump WP3

* revert to 3.2.0

* bump sw-precache-webpack-plugin

* bump back to 3.3.0

* bump dev-server and manifest

They moved it to pundle monorepo 2 months ago

* change error wording and list conflicting files when initializing app

* update code

* Update createReactApp.js

Closes #2713

* Docs for react-router v4 basename feature

Fix https://github.com/facebookincubator/create-react-app/issues/2593

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* dont prompt if serve is already installed

* change name for readability

* Pin the version

Autodetect PyCharm (Pro and CE), WebStorm, PhpStorm, IntelliJ IDEA, RubyMine, CLion, and AppCode

Added IntelliJ IDEA, RubyMine, CLion, and AppCode to list of IDEs. It has the same signature as WebStorm and PhpStorm `<editor> <projectPath> --line <number> <filePath>` so it can reuse the logic from those.

Removed older integrations of AppCode, IntelliJ IDEA

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

Tested with Appcode 2017.1.3, CLion 2017.1.3, Intellij Idea 2017.1.5, PhpStorm 2017.1.4, PyCharm (Pro and CE) 2017.1.4, RubyMine 2017.1.5, and WebStorm 2017.1.4 on MacOS 10.12
Tested with 64-bit CLion 2017.1.3, Intellij Idea 2017.1.5, PhpStorm 2017.1.4, PyCharm (Pro and CE) 2017.1.4, RubyMine 2017.1.5, and WebStorm 2017.1.4 on a Windows 10 VM

Relates to #2636

* Use oneOf to resolve correct loader

* Add html and json fallthrough again

* Use oneOf to resolve correct loader in dev

* Document file-loaders `js` exclusion

* Remove `jsx` from exclusion in prod config

* Update eslint-loader 1.7.1 -> 1.9.0

* Add eslintPath option

* Update eslint 3.19.0 -> 4.1.1

* Update peer dependencies

* Move eslintPath config to outside @remove-on-eject

Jest's default value for this option is ["js", "json", "jsx", "node"].
CRA's current value is ["web.js", "js", "json", "web.jsx", "jsx"], which
is missing one of default ones: "node". This change fixes that.

This "node" extension is used in packages that use native code.

PyCharm has the same signature as WebStorm and PhpStorm `<editor> <projectPath> --line <number> <filePath>` so it can reuse the logic from those.

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

Tested with PyCharm Pro 2017.1.4 on MacOS 10.12

This allows you to set REACT_EDITOR to 'vim --remote', so the file can
be opened in an already running vim process. When using vim without
remote, it works in the same way as before.

When launching vim without --remote, the order of the line and path
arguments doesn't matter. However, when using --remote the line argument
has to precede the path. This happens to be the same as joe and emacs
uses, so the vim cases were just moved there.

I haven't tested this with mvim, but the documentation says the same as
the vim documentation, so I assume it works the same.

Glob support has been added in source-map-explorer@1.4+

 - create-react-app@1.3.3
 - react-dev-utils@3.0.2
 - react-error-overlay@1.0.9
 - react-scripts@1.0.10

* Add changelog for 1.0.10

* Update CHANGELOG.md

* Update CHANGELOG.md

Resolves #2670

Added `gluestick` to the alternatives section

 - react-scripts@1.0.9

* Fix external CSS imports

* Add external CSS import to integration test

* Fix assertion

"Styleguidist combines of a style guide, ..." --> "Styleguidist combines a style guide, ..."

* Bootstrap with Yarn if we can

* Update test scripts

* Check OS and npm concurrency ability

* Windows support

* Update bootstrap.js

* Install yarn before bootstrap

* Add more info about apache client side routing

After a revelation in https://github.com/facebookincubator/create-react-app/issues/2593#issuecomment-311729534

* Update README.md

* Test Node 8 on Travis

We still test Node 7 on AppVeyor

* Update e2e-installs.sh

* Update e2e-kitchensink.sh

* Update e2e-simple.sh

* Update e2e-installs.sh

* Update e2e-kitchensink.sh

* Update e2e-installs.sh

* Update e2e-simple.sh

* Update e2e-simple.sh

* Update e2e-kitchensink.sh

* Update e2e-installs.sh

* Add json and css to lint-staged in template README

This changes the proposed way about using prettier inside the README.md, because prettier supports css since the 1.4.0 release and json since the 1.5.0 release. 

Was not sure if it was a good idea to add different regexes for json and css inside the README.md don't have a real opinion about it myself, could maybe easier for starters to do so if they wan't to add things like eslint or stylelint the the commit hooks.

* Use capitalization for Javascript, CSS and JSON

* Change 'Javascript to JavaScript'

 - babel-preset-react-app@3.0.1
 - create-react-app@1.3.2
 - eslint-config-react-app@1.0.5
 - react-dev-utils@3.0.1
 - react-error-overlay@1.0.8
 - react-scripts@1.0.8

* Add changelog for 1.0.8

* Update CHANGELOG.md

* Update CHANGELOG.md

* Update CHANGELOG.md