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
I want to move the project to Nan because I've tried to build it with 6.9.0 version of Node.js last night and failed due to too many required changes needed (mainly to addon.h), as well to make it easier for wiring-pi to run on newer versions of Node.js. Not to mention that Node.js releases vulnerability bug fixes mainly for the LTS and Future rich versions, which as I state right now are 6.9.1 and 7.0.0.
The text was updated successfully, but these errors were encountered:
Node.js just released
7.0.0
and marked6.9.1
as stable. In answer of this I suggest to switchaddon.h
from "manual Node.js version Addon absraction" to Native Abstractions for Node.js. Nan is the defacto standart for writing Node.js Addons and to keep compatibility between past and future releases of V8 and Node.js. I've used nan in some of my projects and is really easy to use. It will help to remove all redundancies from the macros and make them cleaner. Nan also provides some macros likeNAN_METHOD
to make the life of Addon developers easier.I want to move the project to Nan because I've tried to build it with
6.9.0
version of Node.js last night and failed due to too many required changes needed (mainly toaddon.h
), as well to make it easier forwiring-pi
to run on newer versions of Node.js. Not to mention that Node.js releases vulnerability bug fixes mainly for the LTS and Future rich versions, which as I state right now are6.9.1
and7.0.0
.The text was updated successfully, but these errors were encountered: