browser_wasi_shim
hangover
browser_wasi_shim | hangover | |
---|---|---|
5 | 33 | |
271 | 1,232 | |
- | - | |
8.6 | 8.6 | |
25 days ago | 15 days ago | |
TypeScript | Dockerfile | |
Apache License 2.0 | GNU Lesser General Public License v3.0 only |
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.
hangover
- Hangover 9.0 – Runs simple Windows 32-bit (x86) applications on ARM64 Linux
- Release hangover-8.21 · AndreRH/hangover
- Hangover 8.21 – runs simple Win32 applications on ARM64 Linux
- Hangover-8.15
- Hangover 0.8.5 runs simple Win64/Win32 applications on arm64/ppc64le/x86_64 Linux and x86_64 Mac
- Hangover 0.8.5 Released
- The Tug-of-War over Server-Side WebAssembly
What are some alternatives?
wasi-threads
box64 - Box64 - Linux Userspace x86_64 Emulator with a twist, targeted at ARM64 Linux devices
cargo-wasi - A lightweight Cargo subcommand to build Rust code for the `wasm32-wasi` target
box86 - Box86 - Linux Userspace x86 Emulator with a twist, targeted at ARM Linux devices
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
FEX - A fast usermode x86 and x86-64 emulator for Arm64 Linux
memory-control - A proposal to introduce finer grained control of WebAssembly memory.
RPi4 - Raspberry Pi 4 UEFI Firmware Images
wasmer-js - Monorepo for Javascript WebAssembly packages by Wasmer
design - WebAssembly Design Documents
noah - Bash on Ubuntu on macOS