Moving from Deno to Bun
Loams does not support Deno (D1790, 2026-10-23). The guide to moving a Deno app or tool to Bun, and from Deno Deploy to hosting you own.
Loams does not support Deno. As of 2026-10-23 (design 79, decision D1790), Deno is not a supported runtime or deploy target: the docs no longer list it, and Deno Deploy is not documented. The TypeScript SDK may still run on Deno, but it is not tested there and we do not claim it works. Use Node or Bun.
The reason: on 2026-10-09 the Deno team announced it is joining Cloudflare. It will ship bug-fix and security releases of the Deno runtime for one more year and then end its development, and Deno Deploy shuts down about six months after the announcement. Your Deno code keeps running for now, but it is not a safe place for new work.
The guide
The full guide lives in the Loams repository: Moving from Deno to Bun. It covers installing Bun and the Loams toolchain (Vite+), and moving a Deno app or tool, and its hosting off Deno Deploy, step by step.
Then point your app at Loams with the TypeScript SDK.