NAN 1.6

[kkoopa]

• Added new functions to deal with functions moved from V8 to Isolate. See Changes in v8 between joyent/0.11.14 and io.js/1.0 #225.
• Deprecated NanNewContextHandle in favor of NanNew<Context>.
• Add support for node::Encode/DecodeBytes/DecodeWrite

[kkoopa]

This will not work with node webkit, as they have updated v8, but not indicated it in any detectable way as far as I can see. Too bad.

[rvagg]

@rogerwang is there someone in particular we should pull in for this? nw.js could lose solid native addon support if we can't find a resolution to this.

[kkoopa]

#226 is related for slightly different reasons

[rogerwang]

I'll help to fix this. What do I need to do in nw.js? defining NODE_MODULE_VERSION to some value?

[rvagg]

@kkoopa do we a good have a recommendation here?

@rogerwang if your ABI is the same as some io.js or node release then match the NODE_MODULE_VERSION to that, otherwise make it significantly different. io.js is at 42, atom has jumped to 100. Another alternative is to introduce a new define we can pick up on that talks to your ABI version.

[rogerwang]

It should be the same as io.js. I'll update the io.js in nw.js, so it will be 42. Currently it's some old version (1.0.0).

[kkoopa]

Ah, that would of course explain the mismatch. io.js only bumped NODE_MODULE_VERSION at the last minute before release. Everything should be alright after updating.

[Mithgol]

NW.js v0.12.0-alpha3 was released ≈8 hours ago.

Its inner Chromium is updated to 41 beta (41.0.2272.32) and io.js is updated to v1.2.0.

Does that mean nan support?

[kkoopa]

I guess so.

On February 13, 2015 5:46:14 PM EET, Mithgol [email protected] wrote:

NW.js v0.12.0-alpha3 was
released
≈8 hours ago.

Its inner Chromium is updated to 41 beta (41.0.2272.32) and io.js
is updated to v1.2.0.

Does that mean nan support?

---

Reply to this email directly or view it on GitHub:
#238 (comment)