wasmer-js VS libarchivejs

});

I was then able to just use this code example with one caveat (https://github.com/wasmerio/wasmer-js?tab=readme-ov-file#use...)

I had to update the SDK import with crossorigin="anonymous"

I use https://github.com/wasmerio/wasmer-js and while v0.12 works fine, v1.2 never returns and is stuck in a busy loop internally somewhere. I did not bother bisecting it because the API changed at v1.0.

You can run WASI/WASM modules in the browser using e.g. the (rather simplistic) official WASI polyfill or the more fully-featured wasmer/wasi. So while htis is certainly a bit more combersome than a direct JS FFI, you should already be able to interact with WASI/WASM-compiled Haskell code from JS.

Good spotto! That's the WASI runtime from wasmerjs (https://github.com/wasmerio/wasmer-js).

That's not the WASI runtime being used in this playground. The one in this playground is @runno/wasi-motor (https://github.com/taybenlor/runno/tree/main/packages/wasi-m...). I haven't released it as an NPM package, but it's all MIT so feel free to copy it.

WASI Modules via Wasmer JS

I have good news! Wasmer can also be run on the browser. Check out wasmer-js [1]

[1] https://github.com/wasmerio/wasmer-js/

Maybe wasmer-js could be used by Deno to provide WASI support inside their engine? :-)

7z/RAR/TAR Extraction via Libarchivejs

Another operation that is sometimes desired is to take several files and give the user a compressed file. There are actually a surprisingly large amount (jszip, pako) of client side options here, but my favorite so far when it comes to speed, size and working with .zip has been fflate. But if you'd like to work with other formats, there are also libraries to decompress 7-Zip, RAR & TAR.