Jest v0.5.x moving to io.js

[benhoIIand]

Hi - I updated my Jest version today and received this message about version 0.5.x of Jest:

== NOTICE: ==
On August 1st, 2015, Jest v0.5.x will work only on io.js
Legacy v0.4.x for Node 0.10.x will still be available on
on npm and from the "0.4.x" branch on GitHub.

Could you provide some context as to why this is the case? Is this to say that Jest will only be tested with io.js or it will flat out not work with Node?

Thanks

[stephnr]

Hey @HollandBen, I would recommend reading into it more about Node vs IO.js. There is a merger in place for the two libraries. IO.js is technically a fork of Node.js but will soon be merged back into Node.js at some point.

[benhoIIand]

Ok. I was aware of the merger between Node an IO.js but I've clearly mis-read the message. Just to confirm, until that merger happens, Jest v0.5.x will work only on io.js

[blainekasten]

The message should maybe say something about the eventual merger. Or have a link to an explanation of things as this is likely to freak people who aren't aware of the merger and have hard dependencies on node.

[benhoIIand]

Thanks for the clarification

[DmitrySoshnikov]

Sorry for not to be clear in the message, we should probably rephrase it (feel free to send a PR with the rephrase, although, make sure it's not too big message). We decided to move to io.js in the new versions (since #374), since it's faster (doesn't have dependency on the contextify library we used previously), has more new features, and also jsdom dependency doesn't support legacy Node and also work only on io.js.

The option for legacy Node will still be available via the 0.4.x branch. We'll try to maintain it as well with new features, although would recommend switching to io.js, which eventually will be merged with Node again.

[benhoIIand]

Thanks for the update @DmitrySoshnikov. I'll have to give it a go with io.js and see what the speed difference is like

[blainekasten]

Done @DmitrySoshnikov . #428

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.