MDN updates Compiling from Rust to WebAssembly guide in February 2026

MDN refreshed its "Compiling from Rust to WebAssembly" guide in mid‑February 2026; the documentation page explicitly shows "recent changes within the last week" and presents an up‑to‑date tutorial covering how to compile Rust code to WebAssembly. The republished guide lands amid a flurry of February Rust‑WASM primers and includes guidance that aligns with practical tutorials circulating in the ecosystem.

A practical walk‑through published earlier in the month frames the same toolchain choices. A Oneuptime tutorial titled "How to Build WebAssembly Modules with Rust" by @nawazdhandala, dated Feb 01, 2026, opens with the claim "WebAssembly has changed how we think about web performance" and the author writes, "I have been shipping Rust-based WASM modules in production for a while now, and this guide covers what actually matters when building them." That tutorial pushes the wasm-bindgen and wasm-pack workflow, recommends Node.js and npm for packaging, and states "This tutorial targets node 20."

Tooling details in both the MDN refresh and the Oneuptime tutorial converge on specific Cargo configuration and dependency choices. The Oneuptime guide provides this Cargo.toml example verbatim:

[package] name = "wasm-calculator" version = "0.1.0" edition = "2021" # This tells Rust to build a dynamic library suitable for WASM [lib] crate-type = ["cdylib", "rlib"] [dependencies] # wasm-bindgen handles the JavaScript/Rust boundary wasm-bindgen = "0.2" # Optional but useful for better panic messages in the browser console console_error_panic_hook = "0.1" [profile.release] # Optimize for small binary size - important for web delivery opt-level = "s" lto = true

Oneuptime emphasizes the crate-type setting: "The Cargo.toml file needs specific configuration for WASM output. The crate-type setting tells Rust to produce a dynamic library that wasm-pack can process:" and reiterates that "The wasm_bindgen macro is what makes your Rust functions callable from JavaScript." The tutorial also warns engineers to "Note: Use an up-to-date web server that supports the `application/wasm` MIME type. Older web servers might not support it yet."

Concrete examples in the Oneuptime material show a minimal file layout and both non‑WASM and wasm_bindgen examples. The file tree is presented as:

├── Cargo.toml └── src └── lib.rs

A generated Rust snippet in the tutorial reads exactly:

rust

pub fn add(left: u64, right: u64) -> u64 { left + right } #[cfg(test)] mod tests { use super::; #[test] fn it_works() { let result = add(2, 2); assert_eq!(result, 4); } }

and the wasm_bindgen replacement for src/lib.rs is shown as:

rust

use wasm_bindgen::prelude::; #[wasm_bindgen] extern "C" { pub fn alert(s: &str); } #[wasm_bindgen] pub fn greet(name: &str) { alert(&format!("Hello, {}!", name)); }

The Oneuptime narrative includes the runtime demonstration: "An alert box appears on the screen containing `Hello, WebAssembly!`. We've successfully called from JavaScript into Rust and from Rust into JavaScript."

Developer Mozilla examples included in the collected material mirror the same dependency choice and crate-type guidance, albeit with truncated metadata in the snippet provided. That snippet is reproduced here verbatim and shows the same wasm-bindgen = "0.2" dependency:

[package] name = "hello-wasm" version = "0.1.0" authors = ["Your Name "] description = "A sample project with wasm-pack" license = "MIT/Apache-2.0" repository = " edition = "2021" [lib] crate-type = ["cdylib"] [dependencies] wasm-bindgen = "0.2"

The Developer Mozilla text accompanying that snippet instructs developers to fill in their repository and authors fields, notes that the `[lib]` part tells Rust to build a `cdylib` version of the package, and states that the `[dependencies]` section requests any `0.2.z` version of wasm-bindgen but not `0.3.0` or above.

Timing and recommendations matter: Oneuptime explicitly lists use cases where Rust for WASM makes sense, processing images, running cryptographic operations, parsing large files, and handling computationally intensive tasks, and asserts that "WASM modules typically run 2-10x faster than equivalent JavaScript for CPU-bound work." With MDN showing edits in mid‑February 2026 and the Oneuptime primer dated Feb 01, 2026, the February updates coalesce around wasm-bindgen = "0.2", cdylib crate-type guidance, release‑profile optimizations (opt-level = "s", lto = true), the optional console_error_panic_hook = "0.1", and Node 20 as the target for npm packaging. Expect these specific patterns to shape Rust‑to‑WASM workflows as teams update build pipelines and deployment servers to serve application/wasm correctly.