Anirudha
Product Architect and Builder
Excited about WASM and decentralisation
- Posts
- 147
- Followers
- 18
- Following
- 50
-
Docs got a full rebuild too 📚
Restructured around the three modes (server, exec, OS) instead of the old layout, so the thing you run maps to the section you read. Plus a proper homepage, dark mode by default, and a sweep to correct pages that had drifted from the code.
-
wasmrun 0.21.0 is out. 🎉
Agent mode runs TypeScript and npm packages now. An LLM writes normal TS, imports lodash, POSTs it to /exec, and it runs inside an isolated WASM sandbox. No node on the host, no container per request.
The transpile happens inside the sandbox too, by an swc build compiled to WASI. That keeps the single binary and the isolation model intact, at around 40ms per transpile.
-
npm deps come along with the code:
"dependencies": {"lodash": "^4.17.21"}
wasmrun talks to the registry itself, so there is still no npm binary on the host. sha512 checked, traversal entries and symlinks never written to disk, lifecycle scripts never executed, native bindings rejected with the package named. Pure JS only, which is all the sandbox can run anyway.
-
None of the language support is compiled into wasmrun. Runtimes are WASM modules pulled from wasmhub on first use and cached in wasmrun 🧩
JS runs on the nodejs runtime, TS goes through the swc module first. Both got better this cycle: relative require(), node_modules resolution, timers, Buffer, and the common Node built-ins, plus URL, crypto.getRandomValues and structuredClone.
The nice part is that a new language runtime lands on wasmhub and wasmrun picks it up.
-