Until now, native module (add-ons) maintainers have had to recompile for each Node.js release as well as potentially updating their code to cope with the rapid pace of changes in the v8 APIs. The community API working group has been developing the N-API (Node-API) as a follow on to Nan to help solve this problem and insulate modules from changes in the v8 APIs.
By targeting the new API, modules will be able support a wide variety of Node.js releases without needing recompilation or abstraction layers such as Nan - reducing deployment time and maintenance effort for both module developers and Node.js end users.
With an initial version of the API slated to be part of Node version 8 as an experimental feature, it is a good time to come learn about the shape and usage of the new API from those working to implement it.
Michael Dawson is an active contributor to Node.js and a CTC member. He contributes to a broad range of community efforts including platform support, build infrastructure, N-API, LTS, as well as tools to help the community achieve quality with speed (ex: ci jobs, benchmarking and code coverage reporting). Within IBM he leads the Node.js team driving IBM’s Node.js runtime deliveries and their contributions to Node.js and v8 within the Node and google communities. Past experience includes building IBM's Java runtime, building and operating client facing e-commerce applications, building PKI and symmetric based crypto solutions as well as a number of varied consulting engagements. In his spare time he uses Node.js to automate his home and life for fun.
Arunesh Chandra is working on growing Node.js by extending it to use the ChakraCore engine. He is also working on supporting new ideas in the community like VM Neutrality for Node.js and bringing innovative diagnostic tooling like Time-Travel Debugging to Node developers. https://twitter.com/AruneshC