browser_wasi_shim
haskell-examples
| browser_wasi_shim | haskell-examples | |
|---|---|---|
| 5 | 1 | |
| 271 | 5 | |
| - | - | |
| 8.6 | 5.9 | |
| 24 days ago | 8 months ago | |
| TypeScript | Haskell | |
| Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
browser_wasi_shim
-
Rust + WASM + Typescript [+ React]
There are many options, but what worked best for me is compiling with cargo-wasi and loading the resulting Wasm file with browser_wasi_shim. Using wasm32-wasi instead of wasm32-unknown-unknown requires a bit more work (the communication with JS has to be set up manually), but gives the flexibility of having just a Wasm file that can be dropped in and loaded dynamically. (There's wit-bindgen for generating wrapping code according to an interface definition but I didn't have much success with it.)
- Is it possible to read a file through webassembly?
-
Extending web applications with WebAssembly and Python
The webassembly-language-runtimes is focused on providing WASI-based language interpreters, what would require a WASI polyfill at the browser level (https://wasi.dev/polyfill/) and (https://github.com/bjorn3/browser_wasi_shim).
Pyodide is certainly another option, but is emscripten based, not based in webassembly-language-runtimes or WASI.
-
The Tug-of-War over Server-Side WebAssembly
Indeed, some people are doing this:
- WASI once had an official polyfill https://wasi.dev/polyfill/, now apparently succeeded by https://github.com/bjorn3/browser_wasi_shim
- wasmer-js provides a JS polyfill for WASI https://docs.wasmer.io/integrations/js/wasi
- Cloudflare has a WIP polyfill https://github.com/cloudflare/workers-wasi
I'm generally leery of non-temporary polyfills, so I'm not sure that any of these feel like a long-term viable option for me.
-
Browser to Haskell Wasm Reactor Module Communication Example
Browser client library uses browser_wasi_shim to communicate with the module.
haskell-examples
-
Browser to Haskell Wasm Reactor Module Communication Example
Full example at: https://github.com/hellwolf/haskell-examples/tree/master/2023-02-24-wasm-comm.
What are some alternatives?
wasi-threads
cargo-wasi - A lightweight Cargo subcommand to build Rust code for the `wasm32-wasi` target
webassembly-language-runtimes - Wasm Language Runtimes provides popular language runtimes (Ruby, Python, …) precompiled to WebAssembly that are tested for compatibility and kept up to date when new versions of upstream languages are released
memory-control - A proposal to introduce finer grained control of WebAssembly memory.
wasmer-js - Monorepo for Javascript WebAssembly packages by Wasmer
noah - Bash on Ubuntu on macOS
hangover - Hangover runs simple Win32 applications on arm64 Linux
wee_alloc - The Wasm-Enabled, Elfin Allocator
wasm-pack - 📦✨ your favorite rust -> wasm workflow tool!
team - A point of coordination for all things Rust and WebAssembly
WASI - WebAssembly System Interface
lol_alloc - Like wee_alloc, but smaller since I used skinnier letters in the name.