> Using the previous v8 version in Chromium is harder than using a newer
> v8 version in Node.
> I do want to support the native modules well, so I'm going to add a
> compatibility layer in the v8 Chromium is using to support all the
> deprecated APIs. I hope this can be done in 0.8.x or 0.9.0.
In 0.8.2 the compatibility layer is improved (providing MakeWeak) to
fix bugs when building some modules. If you find other issues please
In future 0.9.0, which will be based on Chromium 32, the differences
between the 2 V8 versions (3.22.24 vs 3.14.5) is too big that
maintaining this layer is not a wise decision any more. While in the
upcoming Node 0.12, the v8 version is almost the same with Chromium's.
So starting from node-webkit 0.9.0, the Node.js come with it will be
updated to the latest Node 0.11.x version. In the same time, node-webkit
0.8.x will be kept maintained and updated until Node v0.12 is released.
Roger WANG Intel Open Source Technology Center
node-webkit: Call all Node.js modules directly from DOM and enable
a new way of writing applications with all Web technologies.