Bun support drops as Deno 2.8 debuts

Bun support is now limited and deprecated

The yt‑dlp project announced that its Bun integration is being limited and marked deprecated. The change appears in GitHub issue #16766, which surfaced on Hacker News and drew 186 points and 135 comments. The discussion centers on the runtime’s stability and maintenance overhead.

Bun, a JavaScript runtime that promises fast execution, had been an optional backend for yt‑dlp’s download logic. The deprecation means new installations will fall back to Node.js or other supported runtimes. Existing users who built scripts around Bun will need to adjust their environments or risk broken builds. The GitHub thread notes that the maintainers will no longer accept pull requests that add Bun‑specific features.

Deno 2.8 hits the blog

Deno released version 2.8 on its official blog, a post that quickly climbed to 216 points on Hacker News. The announcement does not detail every change, but the version bump signals ongoing investment in the secure, TypeScript‑first runtime.

The Deno team highlighted performance improvements and updated standard library modules. While the blog post refrains from marketing language, the community response suggests that developers see the release as a step toward narrowing the gap with Node.js and Bun. The upgrade path is straightforward: users replace their existing Deno binary with the new release, preserving compatibility with most scripts.

Why Bun’s deprecation matters for yt‑dlp users

yt‑dlp is a fork of the popular youtube‑dl downloader, written in Python but capable of delegating network calls to external runtimes for speed. When Bun was first supported, the promise was lower latency for HTTP requests. In practice, a handful of contributors reported intermittent crashes on macOS and Linux, as noted in the GitHub issue.

The limited support now forces developers to either stick with the stable Node.js backend or migrate to Deno, which offers built‑in TypeScript support. For teams that built CI pipelines around Bun, the shift introduces a migration cost: updating Dockerfiles, re‑testing download integrity, and ensuring that any Bun‑specific modules are replaced.

Deno 2.8 in the runtime arms race

Deno’s incremental releases aim to address the same performance concerns that attracted developers to Bun. Version 2.8 arrives less than a year after Deno 2.7, showing a rapid release cadence that mirrors Bun’s aggressive updates. Both runtimes compete for a niche of developers who want a single binary, modern language features, and a secure sandbox.

The Deno blog emphasizes tighter integration with V8 and a more aggressive garbage collector. Those changes could translate into faster script execution, a claim that aligns with the community’s desire for speed without sacrificing stability. While Bun’s deprecation removes one fast option from yt‑dlp’s toolbox, Deno’s continued evolution may fill that gap for projects willing to adopt its ecosystem.

Technical friction and maintenance realities

Maintaining multiple runtimes in an open‑source project introduces hidden costs. Each runtime has its own build chain, dependency graph, and bug surface. The GitHub issue points out that Bun’s API surface was still in flux, leading to frequent breakages that the yt‑dlp maintainers could not prioritize.

Deno, by contrast, follows a more stable release policy and bundles its standard library, reducing external dependencies. This design choice simplifies downstream testing for projects like yt‑dlp. However, Deno’s stricter permission model can require developers to add explicit flags, a friction point for scripts that previously relied on Node.js’s permissive defaults.

What to watch

Developers should monitor the next yt‑dlp release notes for any official migration guide from Bun to Node.js or Deno. On the Deno side, keep an eye on the upcoming 2.9 release blog post for performance benchmarks that may influence runtime choice. The broader JavaScript runtime market will reveal whether Deno can absorb the users displaced by Bun’s deprecation or if a new contender will emerge to claim the speed niche.