-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
✅ All tests that run the CLI should set the
COREPACK_HOME
environme…
…nt variable to use the test-specific Corepack installation directory (#233) All tests in `test/index.ts` except the "CLI should add Git tag with customized tag prefix" test did not set the environment variable `COREPACK_HOME` when running the CLI. As a result, when the CLI tries to run the `npm config get tag-version-prefix` command internally, Corepack downloads npm to the default Corepack installation directory. This caused a segmentation fault and the `npm config get tag-version-prefix` command was aborted by the `SIGSEGV` signal. To fix this, set the environment variable `COREPACK_HOME` in all tests within `test/index.ts` and use the test-specific Corepack installation directory. --------- * ✅ Set the `COREPACK_HOME` environment variable when running the CLI in tests ( 12ca0c1 ) * ✅ All `exec()` functions returned by the `initGit()` function should use the `COREPACK_HOME` environment variable ( f479280 ) All CLI and package manager commands executed within `test/index.ts` should use the `COREPACK_HOME` environment variable. To keep this in mind, we modified our test code as follows: + Add the `execDefaultEnv` option to the `initGit()` function. + Add the `COREPACK_HOME` environment variable to the `execDefaultEnv` option of the `initGit()` function called in `test/index.ts`. * ✅ Fix again problem with "pnpm add" commands failing on Windows ( 333c03c ) I inadvertently caused this problem to reappear in the work on commit f479280. This is a problem that was previously fixed in commit 2613c17. Is it back again? I am probably an idiot. So I added a comment. * 📝 Update CHANGELOG ( c11a224 )
- Loading branch information
1 parent
8dbca9f
commit 5848d67
Showing
3 changed files
with
51 additions
and
27 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters