Relevant: https://nodejs.org/docs/v24.3.0/api/n-api.html
nodejs/node#58852 got me thinking: third-party n-api bindings for quickjs exist but first-party > third-party, so maybe we should add them?
Node.js has comprehensive API coverage in test/js-native-api and that test suite should work, by and large, with any n-api provider.
js_native_api.h is the API surface we'd need to implement. There's some node/V8-specific stuff that doesn't map 1-to-1 to quickjs concepts (e.g. napi_adjust_external_memory) but it's probably okay to fail with napi_generic_failure there.
Relevant: https://nodejs.org/docs/v24.3.0/api/n-api.html
nodejs/node#58852 got me thinking: third-party n-api bindings for quickjs exist but first-party > third-party, so maybe we should add them?
Node.js has comprehensive API coverage in test/js-native-api and that test suite should work, by and large, with any n-api provider.
js_native_api.h is the API surface we'd need to implement. There's some node/V8-specific stuff that doesn't map 1-to-1 to quickjs concepts (e.g.
napi_adjust_external_memory) but it's probably okay to fail withnapi_generic_failurethere.