We're mainly testing Node-API addons being build and published as separate shared libraries in library packages and it would be good to have explicit support for implementing and publishing Node-API addons as part of the app source-code as well.
This could be a few different things:
- As a shared library built as part of building your app, i.e. a multi-arch prebuild included in your app directory. We do support this (as the app package is scanned when we're scanning dependencies for prebuilds), but we're not actively testing it - which we should.
- An addon built as part of your app source-code, this should technically be possible, but we're lacking the merge of PR-104 adding support for the (soft deprecated)
napi_module_register function, which would be the only way to register such a module / addon (as far as I know at least).
A large part of this effort would be implementing an addon in the example app to show the use of the APIs as well as documenting the use-case.
We're mainly testing Node-API addons being build and published as separate shared libraries in library packages and it would be good to have explicit support for implementing and publishing Node-API addons as part of the app source-code as well.
This could be a few different things:
napi_module_registerfunction, which would be the only way to register such a module / addon (as far as I know at least).A large part of this effort would be implementing an addon in the example app to show the use of the APIs as well as documenting the use-case.