node-addon-api VS webidl-napi

If we want it fast, Node-API looks like a perfect solution. A library written in C/C++ must be fast. If you prefer to use C++ over C, the node-addon-api can help. This is probably one of the best solutions available, especially since it is officially supported by the Node.js team. It’s super stable once it is built, but it can be painful during development. Errors are often far from easy to understand, so if you are no expert in C, it might kick your ass very easily.

The Node-API Team proudly announces the release of version 7.0.0 of node-addon-api, the C++ wrapper of the ABI-stable C-based Node-API (npm, GitHub).

Node ffi is an unnecessary wrapper around addon api. See https://github.com/nodejs/node-addon-api

Did a little digging, napi is header file in an npm package that's supposed to help you build C++ addons, node_api is node's actual API. https://github.com/nodejs/node-addon-api you might have already been using this. The examples have enough code that it shouldn't be too bad to get started

Looks like this is known: https://github.com/nodejs/node-addon-api/issues/790

Hey! I work with the NAPI(https://github.com/nodejs/node-addon-api) team and we are in dire need of some help. Dm if you are interested!

Thanks! This seems pretty official. I do really like what I saw from https://napi.rs/ where you just throw a "#[napi]" macro on and it works. Do you know if there's a Node API equivalent C/C++ workflow or tool that does something similar? I think the https://github.com/nodejs/webidl-napi is kinda what I'm looking for but it's archived.