You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm raising an issue here since there isn't a node-bin git repo. I have identified an issue whereby if node-bin is installed without the --save flag then it causes installArchSpecificPackage to be run multiple times as part of the preinstall npm lifecycle hook.
The issue can easily be re-created as per below.
$ mkdir node-bin-test & cd node-bin-test
$ npm i node-bin
Note the version of node being used seems to have no direct bearing on this behavior.
It doesn't matter if a package.json exists or not. As soon as --save is supplied it works fine. I've been able to verify this on other machines.
Seems to work ok with npm@2 but broken in npm@latest & npm@next.
I'm going to raise a separate issue in npm once I can recreate the issue beyond just node-bin but wanted to flag it with you nonetheless.
Cheers,
Jon
The text was updated successfully, but these errors were encountered:
Looks like when npm stages node-bin it gets staged again as part of the arch specific package install, and then continues to be staged again and again until the process is terminated.
Hi @aredridel,
I'm raising an issue here since there isn't a
node-bin
git repo. I have identified an issue whereby ifnode-bin
is installed without the --save flag then it causesinstallArchSpecificPackage
to be run multiple times as part of the preinstallnpm
lifecycle hook.The issue can easily be re-created as per below.
Note the version of node being used seems to have no direct bearing on this behavior.
It doesn't matter if a package.json exists or not. As soon as --save is supplied it works fine. I've been able to verify this on other machines.
Seems to work ok with npm@2 but broken in npm@latest & npm@next.
I'm going to raise a separate issue in
npm
once I can recreate the issue beyond justnode-bin
but wanted to flag it with you nonetheless.Cheers,
Jon
The text was updated successfully, but these errors were encountered: