You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
iojs should only overwrite /usr/bin/node if it was explicitly specified #429
I just found out about io.js and thought it was kind of weird the Mac installer just explicitly stated it was going to alias iojs as node. I use nvm so it didn't overwrite anything but it seems like it would overwrite any node installed by brew or similar.
We had a long thread about this already. This is the future line of development for what was the node executable and should retain the installation path of prior releases.
If you'd like to use multiple versions there is nvm, which is being updated to support io.js as we speak :)
I'm with @mikeal on this too; we're also distributing npm with iojs and I don't see an easy path to making the npm we distribute work with iojs rather than node and nobody wants to encourage users to start adding #!/usr/bin/env iojs to things.
The decision to install io.js should be analogous to deciding to switch to a new stable (well .. perhaps unstable for now) release of Node.js.
I think the best way to get less issues created like these is to better explain (documentation, installation notes, whatnot) to people that the node.js and io.js binaries aren't really meant to co-exist (just to be clear: not talking about the two open source projects here).
perhaps someone in this thread could propose a documentation change to do this, the installers are even in the tools directory so you could even do it there if you think appropriate
FYI after seeing this "co-existing" question come up in IRC many times I've been meaning to have the website team help address via the FAQ or our first "Guide". Ticket now opened: nodejs/iojs.org#64
NVM, and others are the defacto standard for versioning and building node on development machines. Production and staging are different use cases, and lets face it, if your installing IO.js in production, you know what you are doing, and probably not installing node along side it.
Activity
knpwrs commentedon Jan 14, 2015
👍
I just found out about io.js and thought it was kind of weird the Mac installer just explicitly stated it was going to alias
iojsasnode. I usenvmso it didn't overwrite anything but it seems like it would overwrite anynodeinstalled bybrewor similar.mikeal commentedon Jan 14, 2015
-1
We had a long thread about this already. This is the future line of development for what was the
nodeexecutable and should retain the installation path of prior releases.If you'd like to use multiple versions there is nvm, which is being updated to support io.js as we speak :)
rvagg commentedon Jan 15, 2015
I'm with @mikeal on this too; we're also distributing npm with iojs and I don't see an easy path to making the npm we distribute work with
iojsrather thannodeand nobody wants to encourage users to start adding#!/usr/bin/env iojsto things.The decision to install io.js should be analogous to deciding to switch to a new stable (well .. perhaps unstable for now) release of Node.js.
jbergstroem commentedon Jan 15, 2015
I think the best way to get less issues created like these is to better explain (documentation, installation notes, whatnot) to people that the node.js and io.js binaries aren't really meant to co-exist (just to be clear: not talking about the two open source projects here).
rvagg commentedon Jan 15, 2015
perhaps someone in this thread could propose a documentation change to do this, the installers are even in the tools directory so you could even do it there if you think appropriate
snostorm commentedon Jan 15, 2015
FYI after seeing this "co-existing" question come up in IRC many times I've been meaning to have the website team help address via the FAQ or our first "Guide". Ticket now opened: nodejs/iojs.org#64
rvagg commentedon Jan 15, 2015
I'm in favour of closing this issue. Will leave time for other collaborators to chime in and rescue it before I do so though.
miketheprogrammer commentedon Jan 21, 2015
NVM, and others are the defacto standard for versioning and building node on development machines. Production and staging are different use cases, and lets face it, if your installing IO.js in production, you know what you are doing, and probably not installing node along side it.
With that said, I agree issue should be closed.