Cloudflare acquires Deno, and the JavaScript runtime war tilts toward Node

Cloudflare has acquired Deno, according to Fireship. Deno is a runtime for JavaScript and TypeScript that Ryan Dahl announced in 2018 as a correction of his own mistakes in Node.js. He released Node itself in 2009. Eight years after first talking about Deno, Dahl, as Fireship tells it, admits that reimplementing Node was a mistake. The source does not name the price, the closing timeline, or the fate of the products. This is a video review with a description of a few lines, and the material contains no confirmation from the companies themselves.

How the rivalry grew

Node.js appeared in 2009 and made JavaScript a server-side language. In 2018, Dahl gave a talk at JSConf EU titled "10 Things I Regret About Node.js" and showed off Deno. The project is written in Rust, supports TypeScript out of the box, and locks file and network access behind a permissions system. Version 1.0 shipped in May 2020.

Then it became clear that ideology loses to ecosystem. Millions of npm packages are written for Node, and developers did not want to rewrite their dependencies for the sake of a cleaner architecture. Deno made concessions. First came imports via npm, then in October 2024 Deno 2.0 shipped with a focus on Node compatibility. Bun, which makes the same bet, grew in parallel: a fast runtime that runs familiar code.

In September 2024, Deno Land also filed a lawsuit against Oracle, challenging the JavaScript trademark. That is a separate story, but it shows the company was spending effort on more than its product.

Why Cloudflare

Cloudflare already has its own server-side environment for JavaScript. Workers run on V8 isolates, the workerd runtime engine is published as open source, and the nodejs_compat mode adds support for some Node APIs. Deno Deploy occupied a neighboring niche: running code at the network edge. What follows is my interpretation, not a fact from the source: Cloudflare gets a team with deep expertise in V8, Rust, and web standards, and removes a competitor in the edge-execution market.

There is another way to read it. If the creator admits that the path of rebuilding Node turned out to be a dead end, the winner is whoever builds on top of Node rather than in place of it. That is the idea Fireship's headline sells, and it certainly sounds louder than the known facts.

What is known today

• Buyer: Cloudflare. Target of the deal: Deno.
• Source: a Fireship video dated 15 October 2026.
• Price and terms: not disclosed in the material.
• Timeline: Node.js, 2009. Deno announced, 2018. Deno 1.0, May 2020. Deno 2.0 with Node and npm compatibility, October 2024.
• Side news from the same video: JetBrains is giving every account a free coding model, Junie Lite. This is a sponsored segment by the author, and there are no details about the model.

What teams should do

There is no need to panic. If you write on Node, nothing changes: the platform remains the de facto standard, and your dependencies are not going anywhere. If you use Deno, check the support policy and the license, wait for Cloudflare's official announcement, and do not migrate before a roadmap appears.

For projects on Cloudflare Workers, it is worth running your code now with nodejs_compat enabled and seeing which Node APIs are not covered. If you are choosing a runtime for a new service, evaluate not only startup speed but also how smoothly it works with your packages and CI tooling. Judging by this story, compatibility matters more than architectural purity.

You will have to read the details of the deal and the official statements from Cloudflare and Deno in the primary sources.