fix: ignoring .corepack.env with "corepack use" command #788
+25
−1
Conversation
This file contains hidden or 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
Add a test that demonstrates .corepack.env is ignored when running "corepack use <pkg>". The test uses it.fails() to document this as a known issue. Root cause: In BaseCommand.resolvePatternsToDescriptors(), loadSpec() is only called when patterns.length === 0. When a pattern is provided (e.g., "corepack use pnpm"), loadSpec() is never called, so .corepack.env is never read before registry calls are made.
Author
|
@aduh95 Please take a look. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #741
Also adding a test that demonstrates
.corepack.envis ignored when runningcorepack use <pkg>.