bindings also for wasmJS target

[sergeych]

[ionspin]

Hi @sergeych,

this would be nice to add, but I currently don't exactly know where to start with this. Do you have any pointers?

[sergeych]

Hi! I'm as new in new kotlin wamsJS as anybody else, though I would try two aaproaches:

First of all I'm sorry to say I didn't get deep into your nice library guts, so probably things could be easier than I think.

1. Fast and dirty hack. It is possible to use wasmJS-JS interoperability to call your existing JS package (maybe providing some extra JS-friendly endpoints for it). So JS target is compiled first then it's compiled code is used in wasmJS. Though dirty hack, it might work really well and cost less than any other approaches.

2. libsodium itself could be compiled to wasm, probably you already use it in this project? Anyway, the compiled wasm could be called via JS interop (1). In the future it even could be possible to merge compiled libsodium into the same wasm, although I'm sure right now it is too early for it (wasmJS target will most likely change too much so the efforts could be in vane soon).

Actually, at this time (2) is not much better solution than (1), not until we can merge wasm libraries / rust/C code into wasm JS target.

[ionspin]

Those are interesting directions, and you are right, the libsodiumJS library that is used by JS target is wasm produced by emscripten (https://github.com/jedisct1/libsodium.js/), so wasm is already used. Let's convert this into a discussion and keep it open to track the developments regarding wasmJS.