-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] exec
/npx
: npm v8.8+/9+ break with a self-reference
#5777
Labels
Bug
thing that needs fixing
Priority 0
will get attention right away
Release 8.x
work is associated with a specific npm 8 release
Release 9.x
work is associated with a specific npm 9 release
Comments
ljharb
added
Release 8.x
work is associated with a specific npm 8 release
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 9.x
work is associated with a specific npm 9 release
labels
Oct 30, 2022
3 tasks
darcyclarke
added
Priority 0
will get attention right away
and removed
Needs Triage
needs review for next steps
labels
Nov 1, 2022
Duplicate of #5730 |
Nope sorry wrong issue |
Yay, thanks! |
Running the original steps to reproduce, I get a different error with
|
Thanks for noticing; I hadn't had a chance to verify yet. |
Confirmed that my issue is fixed as of v9.1.1, but this can stay open til #5842 lands. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug
thing that needs fixing
Priority 0
will get attention right away
Release 8.x
work is associated with a specific npm 8 release
Release 9.x
work is associated with a specific npm 9 release
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
In a package
foo
with a bin, runnpx foo
, and you'll seesh: foo: command not found
.Expected Behavior
In a package
foo
with a bin, runnpx foo
, and the bin is invoked.Steps To Reproduce
npx [email protected] exec publishers
, see that it invokes the binary properly.npx [email protected] exec publishers
, see that it errors.Environment
The text was updated successfully, but these errors were encountered: