Marcel Klehr
Marcel Klehr
npm has the `npm rebuild` command, yep, just found it as well. Will put a pointer into the README... For 2) this could be integrated into the `nodist global` command...
I agree that separating global modules into different folders is a solution. I'm not sure that differentiating between 32bit and 64bit only is a _sufficient_ solution, though, as native modules...
Another solution came to my mind recently: Fix the node version for globally installed modules. I.e. if you `npm i -g xxx`, `xxx` will always be run with the node...
This does look like a bug. :/ @nullivex Looks like something with the github API lib is broken?
Somehow listAvailable doesn't fail, but just returns nothing: https://github.com/marcelklehr/nodist/blob/master/lib/npm.js#L183 Could it be that we've reached github's API bandwidth limit?
Hey @nwayve! Thank you for reporting this. I will investigate ASAP.
Hi @osher! Nice catch there (and sorry for the inconvenience)! The problem is that nodist uses a binary shim in order to be able to determine node version per directory...
That's exactly how it is. Two layers. Where do you get the third one from? :) Nodist\node.exe is the version that nodist uses internally, it shouldn't be used by anything...
This is fixed on the master branch. I'm still waiting on some feedback for changes to the docs and will release a new version shortly.
Confirmed. It appears signals in golang on windows is not the same thing as signals in node on windows: https://github.com/golang/go/issues/6720 Since there are no signals on windows, Node probably uses...