Question: Using nvm, how does process.execPath returns iojs when initiated with 'node' on Travis-CI?

[am11]

Travis-CI (which uses nvm) possesses a peculiar, but interesting behavior with iojs job: if you run node <command>, it pipes it to iojs. To wit:

# with iojs (v1.2.0) job
iojs -p process.execPath
# will return: /home/travis/.nvm/versions/io.js/v1.2.0/bin/iojs
node -p process.execPath
# will also print the same! instead of /whatever/p/a/t/h/node

How does this happen? If it is due to nvm, I would really appreciate could you point to the location of responsible code.

Thanks in anticipation.

PS: I am trying to explain it here: appveyor/ci#139.

[ljharb]

This is due to io.js itself - node is just a symlink to iojs. This will happen with any io.js install, installed via any method.

[am11]

@ljharb, thanks for your answer. 👍