Fun facts

Trivia gleaned from poking around the Deno repository. None of this is load-bearing — it's just the kind of stuff that's fun to know.

The longest source file in the repo is a test

Not the flags.rs that everyone expects. The longest Rust source file is tests/integration/lsp_tests.rs at 19,909 lines. The runner-up is cli/args/flags.rs at 15,873 lines. Even the third-place finisher, runtime/permissions/lib.rs at 10,921 lines, is shorter.

Lesson: testing the LSP exhaustively requires more code than defining the LSP, the CLI flag parser, or the permission system.

"deno" is an anagram of "node"

This is well-trodden Deno trivia but the codebase makes it official. The Node compatibility layer in ext/node/ and friends contains thousands of lines of polyfills (ext/node/polyfills/) that re-implement Node's API surface in JavaScript on top of Deno's ops. So in some sense "deno" really is "node" — rearranged.

The codebase has been going for almost 8 years

First commit: 2018-05-13. The latest commit at this wiki's snapshot: 2026-04-29. That's just shy of eight years and ~15,755 commits, with v1.0 arriving exactly two years after the first commit (2020-05-14).

bot co-authors are the third-most-frequent committer

denobot has made 108 commits in the recent window, putting it ahead of every individual human contributor except the top six. When you include dependabot[bot] and github-actions[bot], automated commits account for ~3.3% of all-time commits. Bots get things done.

There are 480 TODO/FIXME/HACK comments in Rust

Across the ~504K lines of Rust in this repo, grep finds about 480 instances of TODO, FIXME, or HACK. That's roughly one technical-debt marker per 1,050 lines of Rust — pretty respectable for a project of this scale.

tools/x.ts is Deno scripting in production

The repo's developer CLI (./x build, ./x test, ./x verify) is a single TypeScript file at tools/x.ts (~16K bytes) that runs under Deno itself. The CI workflow files in .github/workflows/ follow the same pattern: ci.ts, pr.ts, cargo_publish.ts, etc., generate the .generated.yml workflow files that Actions actually consumes. Deno's CI runs Deno-the-language to test Deno-the-runtime.

The CLI has a hidden factory module — at 48K bytes

cli/factory.rs is 1,441 lines and ~48KB. It's the dependency-injection container for the CLI: every other file goes through CliFactory to get the configured module loader, npm resolver, type checker, file fetcher, lockfile, etc. Calling CliFactory::from_flags() is what makes "the CLI" work — the rest is mostly subcommand handlers asking the factory for what they need.

There are more web-platform files than you'd guess

ext/web/ alone ships 18 numbered JS files — 00_infra.js, 00_url.js, 01_broadcast_channel.js, … 16_image_data.js — each one implementing a slice of the web platform. The numeric prefixes control the load order during snapshot creation: anything in 00_* is loaded first, then 01_*, and so on, so dependencies between web platform globals are respected.

tests/specs/ is run by a tiny matching language

Spec tests are __test__.jsonc files plus .out expected-output files. The "matching language" in .out files is a couple of macros: [WILDCARD] (any chars across newlines), [WILDLINE] (any chars to end of line), [UNORDERED_START]…[UNORDERED_END] (lines in any order), [WILDCHARS(N)] (next N chars, any). It's just a few helpers, but it lets tests be both deterministic about the important parts and tolerant of paths, line numbers, and timing.

The 1239 author count is misleading

Git counts 1,239 unique committer email addresses across all-time history. A non-trivial fraction of those are duplicates: people changing employer, switching from @gmail.com to @deno.com, GitHub's web-based "noreply" emails, etc. The actual number of distinct humans who have contributed is somewhat smaller — but still a solid couple hundred, which is impressive for a runtime project.