Move to io.js?

[ghost]

Any plan to move to io.js instead of node.js?

---

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

[DinisCruz]

reference links:

• https://github.com/iojs/io.js
• http://www.infoworld.com/article/2854642/javascript/nodejs-gains-a-new-fork-much-to-joyents-dismay.html

[rogerwang]

Yeah. I would like to do that in node-webkit 0.12.0 (this happens to be the next Node.js version ;) . Hopefully the v8 version will be closer with the one in Chromium when it moves on.

[geddski]

@rogerwang is this planned for the near future or further down the road?

[rogerwang]

v0.12.0-alpha1 is released with io.js

[commadelimited]

To be clear, does this mean that "NodeWebkit" is no longer "NodeWebkit" and is now "IoWebkit"? Not trying to be obtuse, but I'd like a clear answer as I'm going to be presenting NW at a conference in May.

The description on the front page of the repo still reads "Call all Node.js modules directly from DOM". I haven't really been following along with the Node/IO split, and I don't really care about it. But I want to make sure I'm communicating the correct information.

[rogerwang]

Thanks for presenting NW. it's like 'io-blink' or 'io-chromium'. io.js remains compatible with the 3rd party modules which referred by 'Node.js modules'.

[OlivierCo]

So good news....