Thank You, Deno
vlt.io
October 16, 2026
7 min read
52/100
Summary
Deno’s team is joining Cloudflare, and the Deno runtime will wind down over the next year. Cloudflare will continue operating the JSR JavaScript registry on its infrastructure, while the team works to merge Deno’s celld technology into workerd, Cloudflare’s open-source runtime for Workers. Ryan Dahl announced the move two years after Deno 2 shipped; Bun joined Anthropic about 10 months earlier. Deno launched in 2020 with deny-by-default permissions, first-class TypeScript, web-standard server APIs, ES modules, a single executable and URL-based dependencies instead of npm packages and node_modules. It later added deps.ts, lock files, import maps and npm compatibility; Deno 2, released in October 2024, added full Node and npm compatibility. The source credits competing runtimes with accelerating Node additions including global fetch, WebSocket, Web Streams, Web Crypto, a stable permission model, type stripping, node:sqlite and require(esm). It also cites competition among package managers as contributing to deterministic lockfiles, workspaces, offline caches, smaller node_modules installations and changes to install-script defaults. GitHub announced in June that npm 12 would stop running install scripts by default after supply-chain worms. The source says a community Deno fork could test demand for an independent secure-by-default, standards-focused runtime.
Key Takeaways
- Deno’s team is joining Cloudflare, which plans to keep JSR running while winding down the Deno runtime over the next year.
- Deno 2 shipped in October 2024 with full Node and npm compatibility after Deno moved away from its original URL-only dependency model.
- Cloudflare plans to merge Deno’s celld technology into workerd, its open-source runtime for Cloudflare Workers.
- GitHub announced that npm 12 would stop running install scripts by default after a series of supply-chain worms.
What the discussion said
The thread mostly mourned Deno as a developer runtime rather than debating AI, so the AI-specific signal is thin. The clearest relevant use case came from a commenter who had adopted Deno as the scripting layer for an agent harness and now expects to move that workload back to Node.js. That reaction matters because agent tooling often depends on small, reproducible command-line runtimes; losing a preferred runtime can force avoidable rewrites in the glue code around models and tools. A smaller thread focused on what the consolidation means for the ecosystem surrounding AI-adjacent infrastructure. Some readers noted that Bun is now tied to Anthropic while Deno is tied to Cloudflare, framing the result as greater corporate backing but less independence. Others pushed back on declaring alternative runtimes dead, arguing that Bun remains notably convenient and capable. Forks were treated as a possible escape valve, including a compatibility-focused fork and a stripped-down alternative, though nobody established that either would preserve the support and stability needed for production AI tooling. The broader argument was not about model quality or safety, but whether runtime consolidation narrows choices for people building automation and agent systems.
Where opinion split
The sharpest split is whether Deno and Bun becoming big-company projects means meaningful runtime competition has ended. Skeptics see consolidation as a loss of independent options for AI-adjacent tooling, while defenders point to Bun's continued usability and emerging forks as evidence that developers still have viable choices.
Community Sentiment
Positives
- Deno proved useful as a compact scripting runtime for an agent harness, showing that its single-binary workflow fit the practical glue work around AI agents.
- Bun is described as increasingly convenient and capable, leaving a credible alternative for developers whose AI tooling needs a lightweight JavaScript runtime.
- Community forks could preserve specialized runtime behavior that agent and automation builders value, rather than forcing every workflow into Node.js.
Concerns
- A developer using Deno for an agent harness now anticipates returning to Node.js, turning a runtime shutdown into migration work for AI automation infrastructure.
- Bun and Deno's ties to Anthropic and Cloudflare raise concern that the runtimes beneath AI-adjacent tools are becoming less independent.
- Forks offer hope but no demonstrated guarantee of long-term maintenance, compatibility, or production support for agent-oriented workloads.
