According to node's release cycle, node6.0 will release at April.
Which version v8 will use in node6.0?
Node6.0 is major update, so it should use latest version when will release.
KiYugadgeter
All 6 comments
Node.js v6 will be using the latest stable version of V8 at the time of its release during April. We are attempting to synchronize with the V8 team to land on V8 v5.0 but because the V8 schedule is not as firm as ours and they have to deal with the variability of the Chromium release schedule there's a possibility that we may be shipping V8 v4.9 in Node.js v6, although we'd prefer to reach v5.0 if we can.
That said, we've also agreed to try some strategies to allow upgrading of V8 during the v6 Stable cycle (some time less than 6 months) depending on how difficult it is to adapt V8 to ensure that we don't break the C++ ABI/API that we export for native addons鈥攖he priority being that a compiled addon shouldn't require a recompile to run on any semver-major version of Node.js, which is historically been very difficult and mostly necessitated us sticking to a single version of V8.
rvagg
on 22 Feb 2016
Cool 馃槉
nicolasparada
on 22 Feb 2016
Where can I find info on the ES/6 features supported in V8 5.0?
hsablonniere
on 22 Feb 2016
@hsablonniere you can look at the features supported by Chrome 50 here: https://www.chromestatus.com/features
targos
on 22 Feb 2016
@targos Thx.
hsablonniere
on 23 Feb 2016
@hsablonniere You can also look here for Chrome 50 (and many other) compatibility questions: https://kangax.github.io/compat-table/es6/#chrome50
jmandzik
on 19 Apr 2016
Related issues
fanjunzhi
路
3Comments
srl295
路
3Comments
akdor1154
路
3Comments
addaleax
路
3Comments
mcollina
路
3Comments
Most helpful comment
Node.js v6 will be using the latest stable version of V8 at the time of its release during April. We are attempting to synchronize with the V8 team to land on V8 v5.0 but because the V8 schedule is not as firm as ours and they have to deal with the variability of the Chromium release schedule there's a possibility that we may be shipping V8 v4.9 in Node.js v6, although we'd prefer to reach v5.0 if we can.
That said, we've also agreed to try some strategies to allow upgrading of V8 during the v6 Stable cycle (some time less than 6 months) depending on how difficult it is to adapt V8 to ensure that we don't break the C++ ABI/API that we export for native addons鈥攖he priority being that a compiled addon shouldn't require a recompile to run on any semver-major version of Node.js, which is historically been very difficult and mostly necessitated us sticking to a single version of V8.