* Adjust the `checkIfOnline` check if in a corporate proxy environment
If the environment variable `https_proxy` is set, test that the proxy name is resolveable rather than 'registry.yarnpkg.com'.
This fixes#2832.
* Adjust to check yarnpkg.com first, then check the proxy address only if that failed
* Allow importing package.json
* Remove package.json import from App.js template
* fix importing package.json
* Rename variable to reflect path is relative to root
* Check for both package & package.json in ModuleScopePlugin
* Use regex to check relative path to package.json
* Strictly enforce package.json extension on scope plugin
* Add allowedPaths to ModuleScopePlugin ctor and use it to allow app package.json
* Remove package.json import from App.js template
* Add package.json to react-scripts/template, show package version and name in the template
* Remove import package.json from template
* Remove template/package.json and its references in code
* Update ModuleScopePlugin.js
* Update README.md
* format UglifyJs error
* move formatBuildError to react-dev-utils
* fix readme
* use regex for plucking the path from stack
* make path human readable and fallback to show error if regex not matched
* rename to printBuildError and add link to the docs
* fix link indentation
* improve readibility + shorten link
Since yarn.lock shouldn't be added to the repo, nor excluded via
.gitignore, lets take advantage of lint-staged to remove any staged
yarn.lock files before they can even be committed.
* Remove note about webpackHotDevClient being webpack 1.0 only
It must work in webpack 2 since create-react-app is still using it and is using webpack 2 now.
It would be great if you could add some kind of note about how it differs from the default webpack hot reloaders.
* Update README.md
* Update README.md
* 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
* 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
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.
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.
