Marcel Klehr

When having set `DEBUG=nodist:*`, running node should give you debug output as well. This probably means, you're not actually running nodist's node.exe. Please check your PATH and make sure there...

The installer should put `path\to\nodist\bin` in your PATH. The system PATH, iirc. It doesn't remove anything from it and doesn't check whether running `node` executes the right binary. Something obviously...

@osher Can you confirm `DEBUG=nodist:*` not producing any output when running `node`? In that case the output of `node -e "console.log(process.execPath)"` would be interesting.

@casz Hi. Which prefix are you talking about? NODIST_PREFIX? Or the prefix of the output of `node -e "console.log(process.execPath)"`? Or something else?

Ahh, interesting. Can you fix it by setting `npm config set prefix "%NODIST_PREFIX%\bin"` in non-elevated prompt? Also, @casz do you experience the same issue with nodist not actually changing the...

Nodist falls back to the local version list if fetching the list of available versions fails. The rationale for not retrying probably was, that it's unlikely that fetching the list...

Ok, so the nodejs.org server is actually [missing](http://nodejs.org/dist/v0.8.27/) the builds for v0.8.27 (see https://github.com/joyent/node/issues/7805)....

Hey there! It's expected that you supply an argument to the npm local command. See https://github.com/marcelklehr/nodist#commands Nevertheless, this case could be handled better than dumping a stack trace :)

Hey! Are you talking about native modules that npm depends on, or native modules that were installed using npm? By default npm is run with the same 32/64 bit version...

ok, so we're talking about packages installed _with_ npm. So, I actually see two problems here: 1) npm doesn't recompile native modules when the node version changes and you run...