Using NAPI-RS with edon to abstract napi interactions and make handling JSValues easier

[karmakarmeghdip]

I am using edon to build tauri-electron-compat to make it easier for existing Electron codebases to adopt and progressively migrate to Tauri. I am planning on implementing Electron polyfill api and the IPC right now is a very rudimentary message passing JSON strings.

Is it possible to use a nice abstraction library like NAPI-RS for creating JS resources to pass to nodejs as a native module?

[alshdavid]

Hi @karmakarmeghdip, in the current version (0.0.27), I have forked & vendored napi-rs and expose it under:

use edon::napi::JsObject;
use edon::napi::Env;
// ... etc

I have a branch that reuses upstream napi-rs, which you can use like this:

[dependencies]
edon = { git = "https://github.com/alshdavid/edon", branch = "extern-napi" }
napi = { git = "https://github.com/alshdavid-forks/napi-rs.git", branch = "alsh/libnode-v2" }

Once this PR is merged into napi-rs, I'll make this the default. Note: I use napi-rs 2.0 in the traget project, but once merged into napi-rs v2 it's easy to add to napi-rs v3