io.js

[xgrommx]

Hello @coreybutler

Do you plan add support for https://iojs.org? It's will be very useful.

[coreybutler]

It's not on my immediate priority list yet. I haven't had much time to play with it yet. At first glance, it looks like the integration process may be a bit more restricted (there is only an msi available). For the moment, I do not have plans to add support, but I will certainly consider adding it as more people start using io.js.

[alubbe]

+1 for iojs

[tracker1]

Should coordinate with nvm-sh/nvm#590 so that the engine syntax is implemented the same...

[midknight41]

+1 for io.js

[mrhyde]

Just letting you know that nvm implemented and merged support for io.js nvm-sh/nvm/pull/616
and io.js now have standalone builds for win-x86 and x64
https://iojs.org/download/release/v1.0.4/win-x64/

+1 for io.js? :)

[coreybutler]

Thanks for the heads up @mrhyde - the standalone installations definitely make this much more feasible within this project.

I'm currently doing a refactor of the project, mostly just cleanup/organization and a new installer. However; I'll at least implement experimental io.js support when I get through this.

[jaylinski]

+1

[tracker1]

Thanks @coreybutler support for this would be much appreciated...

[christoth]

+1, thanks

[takueof]

👍

[iamvdo]

+1

[dshook]

+1. Thanks for the project

[gitjhn]

+1

[vkbansal]

An update from @coreybutler on gitter

Just as an update, I have started work on a 2.x version of this now, but I may release it under a different name since it will be much more robust than the current program. I have not established a release timeline yet, but I am fairly happy with the progress so far, having made many bug fixes for Windows and initial Linux support (OSX is on my mind too). I am committing a lot of time to exploring distribution across all operating systems using tools like yum, apt-get, homebrew, chocolatey, and of course a proper Windows installer.
I will also say that my current plan is still to add iojs support, but I am having hesitations. I've waited, in part, because political issues usually settle given a little bit of time. Since the iojs project is already talking about merging back in with node, it may be a short-lived effort.

[qfox]

👍

[MetaMemoryT]

👍

[t-esch]

👍 Thanks

[ryedog]

👍

[coreybutler]

Since io.js is merging back into node, there is no longer a need to add special support for it.

[tracker1]

@coreybutler sure, wait for a situation to resolve itself... some people are just so lazy... ;-)

[coreybutler]

@tracker1 - haha!

Honestly, I sort of anticipated this... this is the natural pattern. This took about twice as long as I thought it would though!

[alubbe]

meh :(
The merge will still take several months, so it's too bad you won't include it.
How is 2.0 generally coming along?

[coreybutler]

@alubbe - I posted a quick update on the gitter channel regarding progress.

[mickae1]

+1

[pyhedgehog]

nvm needed to switch between different versions. Changing state of current version doesn't removes requirement to support old versions of io.js. Am I wrong?

[coreybutler]

@pyhedgehog - NVM needed to switch between different versions of node, meaning a distinctly different code base from io.js. Since io.js merged the code base with node, current versions of node have all of the io.js features in them.

Basically, you can use old versions of node, but not old versions of io.js.

Does that answer your question?

[pyhedgehog]

@coreybutler Yes.