-
Notifications
You must be signed in to change notification settings - Fork 20
N-API support #53
Comments
Actually, I guess I can choose just any given runtime that supports a given version of N-API? Herm.... some clarification on this would be cool. |
Seems it's difficult to get node-addon-api into the include path reliably. That would be great to have. |
I need to think through the implications of using N-API instead of / adjacent to(?) NaN and just in general with this tool, but I was largely waiting for things to stabilize. I haven't completely kept up with that recently so I'll need to take a look, but I'll put this high on my list for the next major release as I definitely want to support it (it seems like its the intended path forward). |
I've made an napi module using this cmake module. The example can be found here: https://github.com/computerquip-streamlabs/node-win32-np/blob/master/CMakeLists.txt Notice the include_directories statement there for node-addon-api (which is separate from the officially support node_api headers bundled with the runtime itself). This isn't that hard to do frankly and maybe it's better if it's kept separate of the runtime headers regardless. Not sure. |
For the C++ node-addon-api: Just
|
N-API is starting to gain traction. This should have the ability to compile against it similar to a node runtime I feel like.
The text was updated successfully, but these errors were encountered: