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
For what I understand, this have some issues. Correct me if im wrong please.
Supose that I have installed the binaries at /anyDirectory/node/ (Absolute Path)
Then, I have /anyDirectory/node/bin/node, /anyDirectory/node/bin/npm and /anyDirectory/node/bin/npx
So, I expect that executing /anyDirectory/node/bin/npm will use /anyDirectory/node/bin/node even if I have node in the PATH, cause I'm forcing an exact version of npm
And, if I have node, npm and npx in the PATH, and I execute it like npm it will use whatever instance of node is in the PATH
No you're correct. Your expected behavior is the way it used to work, but as I referenced the npm team asked us to change the behavior two and half years ago.
I don't think we're likely to override the request of the npm folks on this one so I think the place to take this up is https://npm.community/. I'm going to close this, but feel free to comment (or re-open if GitHub permits) if there's a reason it should stay open.
Any UNIX version of the Node Binaries like https://nodejs.org/dist/v11.1.0/node-v11.1.0-linux-x64.tar.xz require to have Node inside PATH.
How to reproduce
Ubuntu-18.04-amd64-server./bin/npm --versionor./bin/npx --versionWhat is expected
I expect that runing the above commands work without having Node in the path