Frameworks, the Node.js runtime and AI-assisted code review all depend on TypeScript. Each one now assumes it.

Frameworks came first. Popular ones now scaffold TypeScript projects out of the box. By GitHub's own count, that helped make TypeScript the most used language on the platform in August 2025: about 2.6 million monthly contributors, up 66% in a year, 42,000 ahead of Python.

The runtime followed. Node.js runs .ts files directly. Type stripping has been on by default since v23.6.0 and v22.18.0, and it's stable as of v25.2.0 and v24.12.0. Node erases the type syntax and executes what's left. No build step for most files. Node doesn't check types. The compiler still does that, in CI.

Review is the third. A growing share of code now comes from a model, and a model produces plausible code faster than any reviewer reads it. Types give that code a contract. GitHub's report says type systems catch errors in generated code earlier, and it cites a 2025 study where most compilation errors in LLM-generated code were type-check failures.

A type error is the cheapest reviewer on the team. It reads every line and runs on every commit.

Types also pay for themselves.

A 2017 ICSE study sampled 400 real bugs from public JavaScript projects. Flow and TypeScript could have detected 15% of them. The authors say that likely understates the benefit, since it counted only public bugs and missed the ones developers caught privately. Roughly one in seven bugs, gone before the code runs.

Readability is the larger payoff. Compare two signatures:

The first answers the reader's questions before the body opens. Two numbers go in. A number comes back.

A comment can say the same thing, and nothing complains when it goes stale. A type can't drift from the code, because the compiler checks it. Change the function and the build fails until the signature matches.