docs: clarify yarn dlx version and bin resolution behavior#7100
Open
jarvisz8 wants to merge 2 commits intoyarnpkg:masterfrom
Open
docs: clarify yarn dlx version and bin resolution behavior#7100jarvisz8 wants to merge 2 commits intoyarnpkg:masterfrom
jarvisz8 wants to merge 2 commits intoyarnpkg:masterfrom
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
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.
Summary
yarn dlxaccepts package versions in both the command and-p,--packageformsWhy
Issue #7072 appears partially addressed in code already, but the generated command documentation still omits a couple of practical behaviors that matter in real use: version-qualified packages and the single-package fallback to the sole exposed binary. This keeps the change docs-only and source-backed from the current command implementation.
Testing
packages/plugin-dlx/sources/commands/dlx.tsbehavior