wasm-pack
wee_alloc
Our great sponsors
wasm-pack | wee_alloc | |
---|---|---|
38 | 7 | |
5,937 | 632 | |
2.3% | 0.0% | |
6.4 | 0.0 | |
10 days ago | about 1 year ago | |
Rust | 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.
wasm-pack
-
Rust + WASM + Typescript [+ React]
For a much simpler but less flexible approach there's wasm-pack for creating JS packages from Rust, and wasm-bindgen for easy interop. Both have very good documentation.
-
Tower of Hanoi in P5.js + WASM
After four years, I found some time to pay that deb-tech (yes, quite a long time, eh). To make it fun I rewrote everything from scratch in SolidJS, which went smooth thanks to this amazing library p5js-wrapper. For WASM, C++ is still a good choice, but what about Rust? I did some research and found wasm-pack. A few lines in the cargo.toml file and we were ready to generate compiled + ready to import bytecode!
-
How to Use Rust Code in a JavaScript Worklet (Without wasm-pack)
Support using wasm-pack in Worklets (particularly AudioWorklet) #689
-
Hey Rustaceans! Got a question? Ask here (3/2023)!
If you're looking to use it to interface with node/browsers, then try wasm-pack.
-
Rust WebAssembly (wasm) on Arch Linux with Webpack (Rust 1.66.0)
Webassembly: wasm-bindgen 0.2.83 / wasm-pack 0.10.3
-
Examples of Rust + SvelteKit + WASM
wasm-pack has bugs - it publishes a module which declares itself as a commonjs module. (You can fix that by manually adding "type": "module" in package.json). Then the web build should work with other bundlers. I opened an issue about this over a year ago. There's a PR and everything, but no movement :/
-
Building a web application with Rust and WebAssembly
wasm-pack helps you build Rust-generated WebAssembly packages and use it in the browser or with Node.js.
-
A Look at Performance in Wasmtime and Cranelift
Is the Rust WASM ecosystem being half dead better? wasm-pack and wasm-bindgen are barely maintained anymore, and trust me it's not because everything works flawlessly…
-
Ask HN: Should I learn Rust or Go?
I've been learning Rust for the past few weeks and have been enjoying it a lot.
- The community is very helpful on Discord (https://discord.com/invite/rust-lang-community).
- The package ecosystem (crates.io) makes it very easy to find and import things, and they're consistently documented.
- There's a path to compiling on web via WebAssembly (https://rustwasm.github.io/wasm-pack/)
In a few weeks of learning the language, I managed to put together this visualization: https://twitter.com/admiralakk/status/1542560489091350529
But realistically, either Go or Rust will be fine. You should pick the one you're more likely to stick with and learn, even when it gets tough. I've found the community aspect to be very helpful, because then at least I know I'm not the only idiot out there.
-
Integrating a Svelte app with Rust using WebAssembly
There are various ways to set up a web project that uses Svelte, Wasm, and Rust. For example, wasm-pack from the rust-wasm group provides a template for simple HTML-CSS-JS applications. There are also several project templates for React or Svelte with Rust and Wasm.
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?
trunk - Build, bundle & ship your Rust WASM application to the web.
wasm-bindgen - Facilitating high-level interactions between Wasm modules and JavaScript
wasi-libc - WASI libc implementation for WebAssembly
vite-plugin-rsw - 🦞 wasm-pack plugin for Vite
cargo-wasi - A lightweight Cargo subcommand to build Rust code for the `wasm32-wasi` target
wasmtime - A fast and secure runtime for WebAssembly
create-wasm-app - npm init template for consuming rustwasm pkgs
capacitor - Build cross-platform Native Progressive Web Apps for iOS, Android, and the Web ⚡️
compiler-builtins - Porting `compiler-rt` intrinsics to Rust
cargo-generate - cargo, make me a project
wgpu - Cross-platform, safe, pure-rust graphics api.