Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we implement NAPI? #52

Open
MylesBorins opened this issue Sep 7, 2020 · 3 comments
Open

Should we implement NAPI? #52

MylesBorins opened this issue Sep 7, 2020 · 3 comments
Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested

Comments

@MylesBorins
Copy link
Member

If we do end up implementing support fo WASI (#5) we may want to have a stable ABI for interfacing with V8. I'm not 100% if NAPI would be the best fit but if we can have WASI + NAPI native modules might be portable between jstime + node, which would be pretty awesome.

@MylesBorins MylesBorins added enhancement New feature or request help wanted Extra attention is needed question Further information is requested labels Sep 7, 2020
@ChristopherBiscardi
Copy link

Possibly related is that Neon is also building in support for NAPI: neon-bindings/neon#444

@MylesBorins
Copy link
Member Author

Also worth mentioning web assembly interface types here... I'm not super up to speed on this but I think that there might not be a need for NAPI at all if a webassembly compilation tool chain can manage all of the chatter between native code and the js VM

https://hacks.mozilla.org/2019/08/webassembly-interface-types/

@devsnek
Copy link
Member

devsnek commented Sep 7, 2020

I think having wasi and an api similar to https://github.com/bengl/sbffi/ would cover all the cases we need to support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants