Install wasm-pack with Homebrew

Project links

• Homepage
• Repository

Commands and aliases

• wasm-pack

Project history

The wasm-pack repository was created on February 12, 2018. Mozilla introduced it publicly in April 2018 as a tool for assembling and packaging Rust crates that target WebAssembly, explicitly aimed at letting Rust developers produce npm packages and JavaScript developers consume them without installing a Rust toolchain.

From the start, wasm-pack was described as workflow glue rather than a compiler. It adds the `wasm32-unknown-unknown` target when needed, builds Rust in release mode, runs wasm-bindgen, moves generated files into `pkg`, creates a package manifest, and prepares documentation for the JavaScript package ecosystem.

The Rust/Wasm 2019 roadmap made polishing the toolchain and culminating in a 1.0 version of wasm-pack one of its explicit goals. That placed wasm-pack at the center of the working group's push from experimental Rust/Wasm demos toward stable, batteries-included workflows.

Adoption history

wasm-pack became the default tutorial path for Rust used inside web applications. MDN's Rust-to-Wasm guide teaches the workflow with wasm-pack and explains that the resulting package contains WebAssembly and JavaScript code, so downstream users do not need Rust installed and may not know the implementation language.

The tool's ecosystem role is partly historical. The 2025 Rust post sunsetting the old rustwasm organization marked the end of the working-group hub that incubated tools like wasm-pack, while wasm-bindgen itself moved forward under new maintenance. wasm-pack remains useful and packaged, but it belongs to that first generation of Rust/Wasm workflow tools.

How it is used

A typical project runs `wasm-pack build` from a Rust library crate. The tool compiles for WebAssembly, invokes wasm-bindgen, writes JS and TypeScript-facing artifacts, creates `pkg/package.json`, and can target bundlers, Node.js, or web usage depending on options.

For maintainers, wasm-pack is the packaging bridge: Cargo metadata becomes npm metadata, Rust README material is copied into the package, and the generated JavaScript/Wasm files are laid out so ordinary npm, webpack, or other JavaScript tooling can consume them.

Why package nerds care

wasm-pack is significant because it translated Rust's package culture into npm's package culture. It made a compiled Rust library look like a normal JavaScript dependency, which was essential for early Rust/WebAssembly adoption in frontend and Node workflows.

Timeline

• 2018-02-12: Public GitHub repository created.
• 2018-04-18: Mozilla Hacks introduces wasm-pack to Rust and JavaScript developers.
• 2019-01-23: Rust/Wasm roadmap names wasm-pack 1.0 as a workflow milestone.
• 2024-10-29: GitHub releases show v0.13.1 in the long-running 0.x series.
• 2026-05-15: GitHub releases show v0.15.0 as the latest release at research time.

Related projects

• wasm-pack wraps wasm-bindgen and sits alongside cargo-generate templates, webpack or other JavaScript bundlers, npm, crates.io, and Rust's `wasm32-unknown-unknown` target.

Sources

• https://api.github.com/repos/wasm-bindgen/wasm-pack
• https://blog.rust-lang.org/inside-rust/2025/07/21/sunsetting-the-rustwasm-github-org/
• https://developer.mozilla.org/en-US/docs/WebAssembly/Guides/Rust_to_Wasm
• https://hacks.mozilla.org/2018/04/hello-wasm-pack/
• https://rustwasm.github.io/rfcs/007-2019-roadmap.html
• https://wasm-bindgen.github.io/wasm-pack/book/