Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Proposal] Switch to Nan #60

Open
NoHomey opened this issue Oct 25, 2016 · 1 comment
Open

[Proposal] Switch to Nan #60

NoHomey opened this issue Oct 25, 2016 · 1 comment
Milestone

Comments

@NoHomey
Copy link
Collaborator

NoHomey commented Oct 25, 2016

Node.js just released 7.0.0 and marked 6.9.1 as stable. In answer of this I suggest to switch addon.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 like NAN_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 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.

@nekuz0r
Copy link
Collaborator

nekuz0r commented Oct 25, 2016

Switching to NaN is already a work in progress :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants