npx run existing bins #1906
Closed
npx run existing bins #1906
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
|
LGTM! |
isaacs
approved these changes
Oct 6, 2020
ruyadorno
pushed a commit
that referenced
this pull request
Oct 9, 2020
PR-URL: #1906 Credit: @nlf Close: #1906 Reviewed-by: @ruyadorno
|
How would we force always installing & running a package? (esp if the existing command isn't what I want to run) |
|
@jsg2021 |
|
@isaacs do i have to add |
|
I currently have an automation making a call |
|
I think I'm actually hitting a bug. |
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.
This restores the old
npx foobehavior of looking forfooin the local and global bin paths first, before assuming that it's a package name and attempting to install it.Related to: #1845 and #1746