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
Looks like the version used are quite 'old', v1.5.1, while v2.3.4 is currently shipping! What is the plan to bring this in line with the current io.js release and is there a plan to track those releases.
So in NW.js 0.13.0-alpha3 io.js will be based on the code in 'next 'branch of IO.js. Currently the version number shows 2.3.4, but it would be 3.0 later. And Chromium is rebased to 44.
We had been pending on the old IO.js and Chromium because the v8 versions in them mismatch, see nodejs/node#1451
Looks like the version used are quite 'old', v1.5.1, while v2.3.4 is currently shipping! What is the plan to bring this in line with the current io.js release and is there a plan to track those releases.
In particular io.js ships with many ES2015 (es6) features enabled which is awesome!
Lastly, current releases of both node.js & io.js ship with critical security fixes.
Thanks for the awesome project!
The text was updated successfully, but these errors were encountered: