wasmer-js VS fs

});

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? :-)

You can use File System Standard https://fs.spec.whatwg.org/ to write data for that origin (Firefox doesn't implement File System Access API, nonetheless a File object can still be written to local disk using File API).

Both Firefox and Chromium (Chrome) have implemented WHATWG File System Standard.

Can you just slow down for a moment and focus on what you said?

> We're literally in the discussion about File System API that is:

> - not on any standards track

As others have pointed out the standard is here:

https://fs.spec.whatwg.org/

> - considered harmful by other browser vendors

It is literally being drafted in conjunction by all the major browsers.

> - shipped by default in Chrome

So what? I for one am thankful that Chromium enables features earlier than other browsers. If you don't want the Chromium implementation then don't use it.

Score another point for memfs, the in-memory node.js fe impl.

WHATWG recently took up File System Access spec as their FS spec. It both looks semi promising, but they seem to only care about & are only building specs for specifically emscripten wasm users. Only sync apis, only usable from dedicated workers... there's some hopes for more latter but feels super weird to see the web finally get fs access & have it be fast... but for it to be extremely odd shaped hand tailored to a very narrow class of use.

https://fs.spec.whatwg.org/