Community Calls
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.
Q2 2025 Roadmap: WebAssembly on Kubernetes, HTTP & WASI P3
The April 23, 2025 wasmCloud community call is a special edition dedicated to Q2 2025 roadmap planning. Brooks Townsend reviews how the Q1 roadmap went — 3,500 contributions and nine completed items — then reorganizes the roadmap into research, development, and good first issue categories to give contributors clearer entry points. The biggest theme is hardening HTTP across the wasmCloud ecosystem, including how WebAssembly on Kubernetes should integrate with Envoy, Istio, and ingress controllers. The team also commits to preparing the codebase for WASI P3, moving the workload identity RFC forward, and adopting the XDG Base Directory Specification.
Compiling Go to WebAssembly: Embedding NATS in wash
The April 16, 2025 wasmCloud community call is a study in Go WebAssembly done in anger. Brooks Townsend demos compiling the Go-based NATS server to a WebAssembly module and embedding it directly in the wash CLI — no separate binary, no Docker, no process forked off — so that wash dev can stand up a full local wasmCloud platform from a single static binary. Before that, maintainer Masoud (ossfellow) walks through his provenance-and-attestation RFC — SLSA levels, SBOMs, and the cost of bolting supply-chain security onto a complex monorepo CI pipeline — and the call closes with a heads-up that Q2 roadmap planning lands next week.