Io.js npm capture global?

Question

By setting io.js to node.js, I notice the following weirdness when trying to update node -gyp. When testing npm install -g node-gyp I get the following at the top of the output:

 /usr/local/lib/iojs-v3.3.1-linux-x64/bin/node-gyp -> /usr/local/lib/iojs-v3.3.1-linux-x64/lib/node_modules/node-gyp/bin/node-gyp.js node-gyp@3.0.3 /usr/local/lib/iojs-v3.3.1-linux-x64/lib/node_modules/node-gyp 

I'm a little worried that the io.js installation, or the hack used to update it , somehow changed the way NPM works with the global packaging installation. I also get links to iojs also with other npm commands, for example. with npm install -g npm@latest , so it might seem that npm now either provides special io.js care with some unique log messages, or it doesn’t install for node.js, but rather only for iojs.

• Do node.js and io.js access the same npm global depot?
• Otherwise, io.js will capture the -g destination? in this case, what could be the safest way to get npm back to work with the global node.js depot without waiting for npm to clear at all?

It seems that npm install -g only installs to the io.js path on my system ...