TypeScript 6.0 - The last TypeScript release built on JavaScript
by•
TypeScript 6.0 is the last release built on JavaScript — and the bridge to TypeScript 7.0, which is being rewritten in Go for native speed and parallel type-checking. This release modernizes defaults (strict mode on, ESM-first, ES2025 target), adds built-in Temporal API types, Map.getOrInsert, and RegExp.escape, and deprecates legacy patterns that won't survive the native port. If you write TypeScript, the migration window to the native era starts now.
Replies
Raycast
TypeScript 6.0 marks a pivotal moment in the language's evolution—not due to headline-grabbing features, but for the groundwork it lays.
But if you’re already familiar with the language, you can get TypeScript 6.0 through npm with the following command:
This will be the final release built on the original JavaScript foundation. TypeScript 7.0, currently nearing completion and developed in Go, is set to deliver significantly faster compilation with native code and parallel type-checking.
Version 6.0 serves as the transition point. It updates key defaults (strict mode enabled by default, ESM prioritized, ES5 target dropped), phases out outdated patterns incompatible with the native rewrite, and introduces the `--stableTypeOrdering` flag to assist teams in validating their migration path to 7.0.
That said, there are meaningful upgrades here: native support for Temporal types, `Map.getOrInsert`, `RegExp.escape`, improved type inference for methods, and a default type system update that can boost build speeds by 20-50%.
For teams using TypeScript, this release is the signal to begin preparing. The shift to the native platform is just around the corner.
Launch day is here. Congrats man, @chrismessina!
That "last release built on JavaScript" line is straight fire. So honest it made me stop and pay attention
I took my time going through the homepage. The layout looks super clean and fresh. But lemme tell you what actually grabbed my attention…
You have a section that shows TypeScript catching errors in real time. That's your strongest proof. A developer landing on the page needs to see that right away.
Right now it's under "Adopt TypeScript Gradually." A visitor has to scroll through a wall of code to get there.
So it's better to pull that demo up. Let it be the first thing people see. Show them how TypeScript saves time before explaining how it works.
Just a thought from someone who looks at too many product pages. Attaching the screenshot below:
Spent some time going through it and the structure already feels better. It is less “wall of text” and more guided, which was badly needed still a lot of concepts to wrap your head around, but at least the entry point isn’t as intimidating now