Component Model — typed strings and structs
[![wasmtime-badge]][wasmtime] [![wasmtime-wasi-badge]][wasmtime-wasi] [![wit-bindgen-badge]][wit-bindgen] [![cat-wasm-badge]][cat-wasm]
Core WebAssembly function parameters are limited to i32, i64, f32, and
f64. The WebAssembly Component Model removes that restriction by
adding a language-neutral interface description language called
WIT. Strings, lists, records, and variants all become first-class
types that cross the guest/host boundary without manual pointer arithmetic.
This recipe requires two extra tools:
cargo install cargo-component
rustup target add wasm32-wasip2
Define the interface in WIT
A WIT world declares what a component exports and imports. This one exports a
single greet function that takes and returns a string.
{{#include ../../crates/wasm_component_guest/wit/world.wit}}
Implement the guest
wit_bindgen::generate! reads the WIT file at compile
time and emits a Guest trait. The concrete type Component implements it,
and export! wires it up as the component's entry point.
Build the guest into a .wasm component:
cd crates/wasm_component_guest
cargo component build --release --target wasm32-wasip2
Run it from the host
The host uses wasmtime::component::bindgen! — the same WIT
file, read at compile time — to generate a typed Greeter wrapper. Config
enables the component model, wasmtime_wasi::p2::add_to_linker_sync wires
up WASI Preview 2 (required even for guests that don't use WASI directly), and
Greeter::instantiate produces a handle whose call_greet method accepts a
&str and returns a String.
Run from the repo root (after building the guest):
cargo run --manifest-path crates/wasm_component_host/Cargo.toml
# Hello, WebAssembly!
{{#include ../links.md}}