Marks yarn init as a transparent command
#410
Merged
Conversation
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
merceyz
requested changes
Feb 27, 2024
There was a problem hiding this comment.
This will cause a project with a specific version of Yarn to potentially use a different version for yarn init so we need to solve #202 (comment) first.
aduh95
approved these changes
Feb 27, 2024
|
I agree with @aduh95 - the two problems are separate, I don't think this PR should be blocked until I send a fix for the other one. |
|
Going to work on the "transparent version should be ignored if the local version supports the command" issue in a separate PR. Merging this one in the meantime. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
New projects should use the newest versions when setup. Adding
yarn initas a transparent command means that people running it will automatically have thepackageManagerfield set to4.1.0+sha...unless they explicitly opt-out by runningcorepack yarn@1 initinstead.Projects that don't list package managers will still execute Yarn 1.x, and so will other Yarn commands executed from outside any package directory (
yarn config set, etc).