browser_wasi_shim
wee_alloc
browser_wasi_shim | wee_alloc | |
---|---|---|
5 | 7 | |
271 | 632 | |
- | 0.0% | |
8.6 | 0.0 | |
24 days ago | about 1 year ago | |
TypeScript | Rust | |
Apache License 2.0 | Mozilla Public 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.
wee_alloc
-
Rust + WASM + Typescript [+ React]
As a note, you might find some references to use wee_alloc, but it has been unmaintained for some time and shouldn't be used. I'm using the default allocator with the wasm32-wasi target and it works fine, but I don't know if that works with wasm32-unknown-unknown too; if not there's lol_alloc.
-
Junior Dev here -- How are we setting up Rust, WASM, and webpack?
Note that the wasm-pack tutorial recommends using the wee_alloc crate. This crate is unmaintained and leaks memory, so it should be avoided. Remove this crate, the default allocator works just fine in WebAssembly.
-
Don't use wee_alloc in production code targeting WebAssembly.
It leaks memory: https://github.com/rustwasm/wee_alloc/issues/106
-
Need advice on a project involving Webassembly+ web_sys + webgl
Last thing that comes to mind is switching the allocator to wee_alloc. I use it most of the time for wasm projects and it doesn't make too much of a difference in binary size but that always depends on the project and usually saves at least a few kB.
-
Developing a cross-platform game for browser, Ios, and Android using rust?
For example, check out wee_alloc.
-
Rust on the front-end
wee_alloc, an allocator optimized for small code size.
-
#![no_std] with WASI is more complicated than I thought it would be
Ok. Now I need to add in a global allocator. I use wee_alloc since I know it works pretty well with WASM: Cargo.toml
What are some alternatives?
wasi-threads
wasm-bindgen - Facilitating high-level interactions between Wasm modules and JavaScript
cargo-wasi - A lightweight Cargo subcommand to build Rust code for the `wasm32-wasi` target
wasi-libc - WASI libc implementation for WebAssembly
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.
create-wasm-app - npm init template for consuming rustwasm pkgs
wasmer-js - Monorepo for Javascript WebAssembly packages by Wasmer
compiler-builtins - Porting `compiler-rt` intrinsics to Rust
noah - Bash on Ubuntu on macOS
wasm-pack - 📦✨ your favorite rust -> wasm workflow tool!