Rust outlines 2026 Wasm Components goal, adds wasm32-wasip3 and web targets

Rust has pushed a concrete 2026 Wasm Components goal that adds a wasm32-wasip3 target and explicit web/component targets while routing work to the compiler and libs teams; the project frames this as practical target additions tied to tiering and experimental language work. The Rust project is operating at scale: the September 2025 blog reported "The Rust project is currently working towards a slate of 41 project goals, with 13 of them designated as Flagship Goals," placing Wasm Components among a crowded but prioritized roadmap.

The rust-project-goals page for Wasm Components is summarized on the project goals site and, in the project's own words, "Who and when: The Rust project goals site published a detailed page describing the 'Wasm Components' goal for 2026; the page is part of the 2026 goals collection and lays out concrete target additions, tiering plans, and experimental language work the compiler and libs teams intend to pursue. The do" — the published excerpt is truncated at that point, but it explicitly promises target-level detail and team responsibilities. That tracking model matches the blog's workflow: "The full details for any particular goal are available in its associated tracking issue on the rust-project-goals repository."

Named points of contact and champions in the project's tables show how work will be assigned. The "Unblocking dormant traits" and related goal tables list Taylor Cramer as point of contact for evolving trait hierarchies and associate Oliver Scherer with types; Alice Ryhl is listed for in-place initialization; Rémy Rakic is tied to stabilizable Polonius support on nightly. Compiler- and build-related efforts that cross-cut wasm work are explicit: David Wood is point of contact for build-std with cargo champion Eric Huss and libs champion Amanieu d’Antras, Sparrow Li is listed for Promoting Parallel Front End, and Folkert de Vries is named for a production-ready cranelift backend.

The project's design work already surfaces language-level issues that matter for componentized Wasm. The September 2025 blog includes a design section that opens, "There are two categories of projections: Containers and Pointers:" and enumerates concrete examples such as MaybeUninit<T>, Cell<T>, UnsafeCell<T>, NonNull<T>, and Pointer<'_, Field>. That same post records the projection problem and the Rust-for-Linux motivating example: "We want to be able to have both a blanket `impl<T, F: Field<Base = T>> Project<F> for &T` as well as allow people to have custom projections on `&Custom<U>`. The motivating example for custom projections is the Rust-for-Linux `Mutex` that wants these projections for safe RCU abstractions." The post also notes a design-meeting suggestion about adding a compiler-only generic to Project and then states, "We have now found an alternative approach that requires less specific compiler magic:" before the excerpt ends.

Community-facing tutorials and explainers already point toward the same use-cases the goal targets. A December 23, 2025 Medium guide outlines building Web Components "natively" in Rust with wasm-bindgen, web-sys, and helper crates like rs_web_component and promises to "Look at the WebAssembly Component Model, which takes the idea of components beyond the browser and into a language-neutral, WIT-described world." An InfoWorld YouTube tutorial from March 25, 2025 shows hands-on steps for a simple Rust→WASM module and, in its transcript, states verbatim that the "web assembly tool chain for rust which comes in the wasm pack crate and we install that with cargo install W and pack again" and that a sample function "takes in a string it reverses it and returns another string" — the video had 3,075 views and illustrates existing practitioner demand for wasm tooling.

If the wasm32-wasip3 and web/component targets land as outlined, the work will concentrate across named maintainers and teams already listed in the rust-project-goals tables - Taylor Cramer, David Wood, Folkert de Vries, Amanieu d’Antras, and others - and will surface the Polonius, build-std, and projection design work already under discussion. The next concrete place to watch remains the rust-project-goals tracking issue for Wasm Components and the associated compiler and libs threads where those champions are listed.