Image: JetBrains
Why it mattersA React or Angular team on WebStorm can move to the Go-based language service by changing one preference, keep its existing TypeScript version, and stop waiting on the Node.js language server between keystrokes.
JetBrains has released WebStorm 2026.2.2 with stable support for TypeScript 7, Microsoft's Go-based rewrite of the TypeScript language service. Piotr Tomiak, who wrote the announcement, says React and Angular projects can turn the engine on in preferences with no project changes and no requirement to move off an older TypeScript version.
The switch matters because TypeScript 7 replaces the Node.js-based language service. JetBrains cites Microsoft's own numbers that the new compiler is "up to 10x faster than its Node.js-based predecessor", and quotes internal testing on the Kibana codebase where project load dropped from around 12 seconds to 3 seconds. Coding assistance draws on the same engine, so completions and diagnostics get the same speed-up.
What is included
React support in 2026.2.2 is stable on the standard TypeScript 7 flow. Angular needed extra work: neither the Angular compiler nor VS Code supports TypeScript 7 for Angular templates yet, so JetBrains ported an Angular template transpiler to Kotlin and added a mapping layer on top of it that translates IDE requests from original source coordinates to the generated code. Tomiak says Angular support is fully stable in this release.
Vue is not stable yet. Tomiak writes that JetBrains is "porting the Vue transpiler to Kotlin and Kolar" and is still working out how to support Vue with TypeScript 7. One caveat named in the post: the TypeScript-Go content-mappers feature is limited to non-TypeScript files today, so it will not cover Angular use cases through that path.
Teams that must stay on an older TypeScript version, for library reasons or because a build system cannot update yet, do not need to change anything to get the new engine. The IDE's TypeScript version selection is separate from the language service engine, so a project on TypeScript 5.x can still use the TypeScript 7 service for editor work. That is the practical difference between using it today and waiting until every build tool supports it.
The line with the most risk for adoption is JetBrains' own phrasing: "The result is a faster compiler that does less work to deliver the same or better coding assistance." Whether it delivers the same or better assistance in each stack is now something a React or Angular team on WebStorm can test in its own repo, in one preference toggle, without touching the codebase. If completions or diagnostics regress, the same toggle switches back.
Source
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.
