The numbers are hard to argue with. TypeScript hit 2.64 million monthly contributors on GitHub in 2025, a 66% year-over-year jump, with over a million developers writing their first TypeScript code on the platform. GitHub’s October Octoverse report called it the largest language ranking shift in a decade. Stack Overflow’s survey data backs it up: 66% of nearly 49,000 respondents reported using JavaScript, a dominance streak running since 2011.

Here’s the part that should make anyone who predicted AI would make language choice irrelevant uncomfortable. Two years ago, the assumption was that coding agents would turn organizations stack-agnostic — pick whatever fits the business problem, hiring pool be damned. Instead, the opposite happened. The market narrowed, hard, around one language family.

The mechanism is straightforward and a little depressing. Models write best in the code they’ve seen most. Most published code is JavaScript and TypeScript, much of it centered on React. Ask an agent for a typed React component and you get something that compiles, matches codebase standards, and needs minimal edits. Ask for Svelte or Solid and you get thinner output, invented APIs, and scaffolding that needs real corrections before it runs. Teams noticed. They now pick stacks based on what their tools generate well, not what’s technically best. That output gets published, scraped, and fed into the next training run, widening the gap further.

GitHub’s take is that type systems became the guardrail for generated code. Agent-written code reads well and runs fine in dynamic languages — until shape mismatches crash it three calls down. TypeScript catches that before execution. Meanwhile, the AI stack itself is still built in Python, but the products are shipped in JavaScript. By late 2025, GitHub counted over 1.1 million public repositories using an LLM SDK, a 178% annual increase, driven almost entirely by application development rather than model work. Every enterprise pilot past the demo stage needs a front end, and JavaScript frameworks own that space.

The uncomfortable implication: AI didn’t flatten the tech stack landscape. It paved a highway through it, and that highway runs through TypeScript.