There’s a common tool included in Hadoop that also has a `yarn` command,
which created issues for users who had Hadoop installed:
* #1257
* #1363
Yarn also installs the command under `yarnpkg` alias (added in
cefa9a368d)
so we can use `yarnpkg` instead of `yarn` to make it more reliable.
This has no effect on users who don't have Hadoop installed, but those
who have won't see errors from falsely detecting Hadoop Yarn as Yarn
the package manager, and they can now also install Yarn to make use of
our Yarn support without the Hadoop Yarn interfering.
* Use "commander" for cli argv handling
* Handle different scripts version forms and exits without a name given
* Revert comment about min supported node version
* Check sooner for the minimal node version
* Add travis test for node <4
* Parse stderr in node versions <4
* Remove the “‘yarn’ is not recognized as an internal or external
command, ...” message on Windows
* Simplify the detection code: just run `yarn --version` – if it
succeeds use `yarn`, if it fails use `npm`.
- Use “Chrome” instead of "Google Chrome", It will try to use current active browser.
otherwise, use default.
- If “Chrome”s aren’t running, will fallback to opn(url)
* Let Jest handle all file types
* Update regexes
* Fix exclusion regex to also exclude files without extension
* Be over-cautious with Windows paths because I'm not sure how Jest handles them
* There is no automatic babel-jest discovery now that we use transsform
* Reuse empty tab on open chrome apple script
* Break find tab into function
* Use property to store found
* Fix minor issues that caused window to not get active
* Don't strip stack traces of evaluated webpack code
* Strip stack traces at the end of a string
because the last line doesn't always have a `\n` and `create-react-app` is leaving the last line of the stack traces present in the error messages
* code comment
* code comment
In my tests, jsdom was throwing a "SecurityError" at HistoryImpl._sharedPushAndReplaceState (node_modules/react-scripts/node_modules/jsdom/lib/jsdom/living/window/History-impl.js:87:15)
This happens because document.URL defaults to "about:blank". Unfortunately, if you interact with the History object it tries and fails to parse the URL, causing a "SecurityError" to be thrown. Setting the default URL to "http://localhost" fixes this issue.
Jest matches moduleNameMapper regexes with module names, not the full
file path, so the negative lookahead doesn’t work for filtering out
JS files, because they can be imported without the extension. So paths
like `lodash.assign` and `../utils/range` were mislabeled as resources
with unknown file extensions because they have a dot in the name.
As a stopgap measure, revert the moduleNameMapper regex added in #1077.
* Added functionality to crash the build during CI whenever linter warnings are encountered.
* Updated the docs with a description on how to use the build in CI
* Fixed small typo
* Fixed description of build error.
