Do More in the Browser with Wasm Components
summary
Converts Web IDL into a reusable browser.wit package so non‑JS languages can call DOM APIs; a single proxy of the global object and a generated glue layer (claimed to be <100 lines) maps calls into JS. Uses a jco transpiler and WASI runtimes to run Rust and Python components in the browser; examples include a 79 KB hello, a 562 KB GitHub manager, and one 138 MB outlier. Runs server‑style components inside a service worker that intercepts HTTP requests so full apps run client‑side; promise integration is in Chrome origin trial.
AI-written summary · about
chapters (8)
- 0:00Introduction to Wasm
- 0:50The component model and WIT
- 2:18Bridging web APIs with WIT
- 4:58Web component demo
- 6:31Transpilation with JCO
- 8:32WASI browser challenges
- 11:04Service worker demonstration
- 17:26Q&A and final discussion
related talks
18mAn introduction to the WebAssembly component model
50mWeb Assembly
39mJavaScript Toolchain for WebAssembly Components
56mKEYNOTE: WebAssembly Update: The Proposals, Wasi, And The Component Model
32mBringing WebAssembly outside the web with WASI
34mWasm Components for Every Language
37mBeyond the browser: Moving forward with a more Declarative Future with WebAssembly
48mWebAssembly Beyond the Browser
