adapt to node 4.0.0 about hxnodejs HOT 6 CLOSED

How will we handle versioning in hxnodejs? Will we use @:require? Or separate branches?

from hxnodejs.

well, for this particular nodejs release (which is long-term-support) i tend to just adapt hxnodejs to latest apis and finally do the haxelib release, for further releases I think branches would be better than @:require branching spaghetti.

from hxnodejs.

I think Git branches is also more manageable!

2015-09-08 17:40 GMT-03:00 Dan Korostelev [email protected]:

well, for this particular nodejs release (which is long-term-support) i
tend to just adapt hxnodejs to latest apis and finally do the haxelib
release, for further releases I think branches would be better than
@:require branching spaghetti.

—
Reply to this email directly or view it on GitHub
#41 (comment)
.

[image: Imagem inline 1]

from hxnodejs.

4.1.0 https://nodejs.org/en/blog/release/v4.1.0/

from hxnodejs.

Tho there seem to be no API changes.

from hxnodejs.

hxnodejs is now targetting nodejs 4.0+

from hxnodejs.