1. createRequire should have been properly handled in newer Jest
versions: https://github.com/facebook/jest/pull/9469
2. We don't test migrators with Jest mock modules anymore
So it's safe to skip that condition
* fix: should infer package manager from config if there's no lockfile in the project
* fixup! fix: should infer package manager from config if there's no lockfile in the project
* Replace chalk.reset with stripAnsi
When logging multi-line logs, the logger uses chalk.reset in order to get the length of the tag for the log. This is to achieve an indented layout of multi-line logs. chalk.reset only replaces styles such as bold and italic, not color. When the tag contains colors, the result is not pretty. Replacing with stripAnsi gets the intended result.
* Adds reference to strip-ansi
* Removes misplaces comma from package.json
* Removes extraneous semicolon
* fix: add pnpm v4 support
in pnpm v4 the option '--loglevel' is no longer available instead '--reporter' is used.
* refactor: remove 'v' from PNPM constants for linting
* refactor: rename variable
* fix: typo in _hasPnpm4orLater
Co-Authored-By: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
* refactor: reduce the amount of duplicate code for pnpm version check
* refactor: remove return-assignment
* refactor: add explicit return value instead of using array access
Co-Authored-By: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
* fix: remove return value from checkPnpmVersion
* fix: pnpmVersion variable
* refactor: cache pnpm version number
* refactor: fix function name and revert api break
* fix: function call correction
* refactor: export hasPnpmVersionOrLater and use this in favor of hasPnpm4OrLater
* refactor: move cache getter into getPnpmVersion
* refactor: add comment
* refactor: remove comment
It has become a common source of mistakes.
For example, during PR #4363 I've referred to the wrong `options`
several times due to the variable shadowing.
- We never referred to `yarnpkg` anywhere else in the codebase
- For the rare case that `yarn` binary is overridden by Hadoop YARN,
`yarn --version` will throw (it only supports `yarn version`), therefore
it won't pass this check.
Fixes#3941.
Closes#3942.
