News for hackers. Stuff that matters.

A comment on Io.js 1.0.0.

Re:Io.js 1.0.0 by acdanger on Tuesday January 13, 2015 @11:05PM (#8884225)
"This package will install io.js v1.0.0 and npm v2.1.18 into /usr/local/. The binary /usr/local/bin/iojs will also be symlinked as /usr/local/bin/node."

Why the symlinking as node?

[ Parent | on HN ]
Re:Io.js 1.0.0 by Killswitch on Tuesday January 13, 2015 @11:06PM (#8884231)
Because Io.js is a Node.js replacement, but most of the time you're probably going to instinctively type `node script.js` and not `iojs script.js` so the symlink is just a helper.
[ Parent | on HN ]
Re:Io.js 1.0.0 by solomone on Tuesday January 13, 2015 @11:14PM (#8884257)
It's for bin scripts such as NPM which refer to the executable directly. See here: https://github.com/iojs/io.js/issues/249
[ Parent | on HN ]
Re:Io.js 1.0.0 by adregan on Tuesday January 13, 2015 @11:52PM (#8884383)
Homebrew asked me to overwrite my node symlink with the iojs symlink. I decided to link iojs to iojs on my own. I hope I'm not spinning myself into some technical debt here, but for now, I'd like to maintain both.
[ Parent | on HN ]
Re:Io.js 1.0.0 by ChiChou on Tuesday January 20, 2015 @11:27AM (#8917650)
Some npm modules require specific version of node. If iojs overwrites `node` you may see node-gyp use algernative fallback build, which causes installation failure. At least now, the better way is to keep symlink to node as node. Use iojs when needed.
[ Parent | on HN ]