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

Resolves #2670

 - 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, ..."

* 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

* 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

* Fix a command style in docs

* Add a link to docker's docs

* Better React Native Web support

* Adding better react-native-web support for jest testing

* Minor code style edits to user guide

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* 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

* 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++