This repository has been archived by the owner on Apr 7, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 71
[BUG] Unexpected binary invoked #77
Comments
npx takes a package name, not a bin name, and selects the first One workaround might be to create a fourth binary that can dispatch to the other three, and put that first? (or even, to make that the primary interface for the package and only provide one binary) |
Would there be any implications in improving the logic, so it's a binary which matches the package name that is picked (only if it's found, otherwise it could be first in a list, as it happens now) |
medikoo
added a commit
to serverless/components
that referenced
this issue
Aug 25, 2020
It's to ensure we're not affected by npm/npx#77
medikoo
added a commit
to serverless/components
that referenced
this issue
Aug 25, 2020
It's to ensure we're not affected by npm/npx#77
medikoo
added a commit
to serverless/components
that referenced
this issue
Aug 25, 2020
It's to ensure we're not affected by npm/npx#77
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current Behavior
I've run following in context of some local package:
With
github-release-from-cc-changelog
neither being available locally or globallyInstead of
github-release-from-cc-changelog
binary npx invokesdump-release-notes-from-cc-changelog
binaryExpected Behavior
It's
github-release-from-cc-changelog
binary that should be invokedI'm using
npx
as bundled with npm v6.14.7 (not exactly sure which version of npm is that, as npx -v outputs npm verison)The text was updated successfully, but these errors were encountered: