-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
compat: tracking issue for running npm #13187
Comments
When trying to run
|
@bartlomieju I can't reproduce the above error on my machine. How do you execute npm? |
BTW I use |
I got it cloned locally, and I execute it like: |
This seems like an issue with |
|
|
Wow. Great! Thanks! @AaronO |
Tried on my machine. I still see this kind of error (with
What version have you tested? |
nevermind. I found the cause. Will send a PR to std soon |
Just checked again, and I still can't run latest version of npm (v8):
|
npm
(show help message) ✅process.execPath.toUpperCase()
npm/lib/npm.js:213
feat(node): add process.execPath std#1748npm ERR! Exit handler never called!
at the end of the execution node: 'exit' event is emitted twice when process.exit() is called std#1752npm init
vm.runInThisContext
callpromzard/promzard.js:86
in promzard feat(node): add vm.runInThisContext std#1747npm ERR! Exit handler never called!
at the end of the execution node: 'exit' event is emitted twice when process.exit() is called std#1752npm install <dep>
minipass-fetch/lib/index.js:73
in minipass-fetchnpm ERR! request to https://***:[email protected]/pretty-bytesnullnullnullnullnullnull failed, reason: this.cb is not a function
looks enigmatic. Something's wrong with https.request?The text was updated successfully, but these errors were encountered: