Community Calls
Testing Wasm Component Model Functions with wasmtime run
The May 28, 2025 wasmCloud community call is a short, hands-on session about testing Wasm component model functions. Brooks Townsend demos wasmtime run --invoke — a new flag in Wasmtime 33 that calls any exported function on a WebAssembly component directly from the command line, passing strongly typed arguments via the WebAssembly Value Encoding (WAVE) syntax. That sparks a discussion about bringing the same ergonomics to wasmCloud's wash call. The team then reviews the Q2 2025 roadmap, and Florian Fürstenberg presents a detailed investigation into why an overloaded Hello World component can deadlock the whole application — tracing it to wRPC handshakes, NATS subscriptions, and the host's invocation semaphore.
A Year of wasmCloud 1.0: WASI, the Wasm Component Model & 2.0
The May 21, 2025 wasmCloud community call is a short, reflective one centered on the Wasm component model and the standards beneath it. Brooks Townsend walks through his new blog post celebrating a year of wasmCloud 1.0 — built on WASI 0.2, WIT, and the component model — and the deliberate bet on WebAssembly standards that drove community growth. Taylor Thomas and Liam Randall look ahead to wasmCloud 2.0, WASI 0.3, and a more pluggable host shaped by user design feedback. The call closes with an Issue of the Week and a Documentation of the Week highlighting a new capability-provider icon.
wRPC Error Handling & axios in a Wasm Component Model App
The May 14, 2025 wasmCloud community call brings back the "Documentation of the Week" and "Issue of the Week" segments and digs into two practical threads in the Wasm component model. Brooks Townsend walks through the experimental error handling for custom interfaces landed in wasmCloud 1.8 — where wRPC surfaces platform-level transport errors to the guest instead of panicking — and turns the gap in its docs into an Issue of the Week. Victor Adossi then demos a new TypeScript example that runs the popular axios HTTP library inside a WebAssembly component, and the team gives kudos for a new cron job capability provider and per-component memory limits.
WebAssembly News: NATS Stays in the CNCF & the wasmCloud Q2 Roadmap
The May 7, 2025 wasmCloud community call is a quick, agenda-free update led by Brooks Townsend — and the WebAssembly news at the top is the one a lot of people were waiting on. The CNCF and Synadia have aligned to keep the NATS.io project under the CNCF, with its Apache 2.0 license intact and the trademark remaining with the CNCF. With that uncertainty resolved, Brooks walks wasmCloud's transport-agnostic push with wRPC and the Q2 2025 roadmap: custom interfaces, good first issues, NATS provider diagnostics, the XDG base-directory move, a host configuration file, outgoing HTTP client tracing, and an event publisher abstraction.
Hono on Wasm, Component Saturation Metrics & the NATS Statement
The April 30, 2025 wasmCloud community call centers on the Wasm component model and the JavaScript ecosystem reaching it. Milan Raj demos the Hono web framework compiled to WebAssembly with JCO and TypeScript — JSX server-side rendering, OIDC authentication, and a fully typed OpenAPI service — showing how much of the JS ecosystem just works inside a component. Brooks Townsend then demos new component-instance saturation metrics over OpenTelemetry, walks a large refactor that makes the wasmCloud host embeddable behind pluggable traits, and leads a candid community discussion on the proposed CNCF NATS.io licensing and ownership changes.