How do NAPI works compare to WASM, and what are the use cases suiting each one?

• slime_seed_finder

  6 49 7.3 Rust

I use both of them in my project slime_seed_finder, WASM to run the app in github pages, and NAPI to use the same frontend inside a native electron app. The bindings are in the slime_seed_finder_web and slime_seed_finder_webnode folders, respectively. The electron app is still work in progress so I don't know if the final version will still use NAPI, so far I have found many problems when trying to use it. The good thing is that it is easy to generate bindings for either case, so I don't need to change the main app logic, the main difficulty is passing non-primitive types back and forth.

• node

  932 103,970 9.9 JavaScript

  Node.js JavaScript runtime ✨🐢🚀✨

  

You have a valid point, but I will make a counterexample: the QUIC API for node was initially estimated as a 1 month job, it has now been pending for 3 years. And heavyweights like James Snell and Matteo Collina working on it.

• SurveyJS

  surveyjs.io featured

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

Suggest a related project