Users of WebStorm 2026.2.2 can now select the Go-based TypeScript 7 engine to obtain faster coding assistance in Angular and React projects, according to JetBrains. Enabling the support does not require changing the TypeScript version on which the project depends, meaning that teams restricted to an older version for infrastructure-related reasons can benefit from development environment improvements without carrying out a migration.
What Changes Inside WebStorm?
TypeScript 7 replaces the Node.js-based language service with a new engine written in Go. JetBrains says this change reduces the work performed by the compiler to reach a comparable or better level of coding assistance, with the impact becoming more apparent in large codebases.
WebStorm did not rely solely on the existing plugin layer; it rebuilt the integration at the language-service level to provide native support for the new engine. According to the post, official Microsoft builds indicate that the new compiler may be up to ten times faster than its Node.js-based predecessor. When testing TypeScript 7 on the Kibana codebase, JetBrains also recorded a reduction in project loading time from about 12 seconds to 3 seconds.
Angular Support Through a Dedicated Integration
Stable support for Angular projects arrives in WebStorm 2026.2.2 and can be enabled from the program preferences without modifying project files. JetBrains explains that this became possible despite the Angular compiler and coding assistance tools in VS Code not supporting TypeScript 7.0, because WebStorm uses a dedicated adapter for Angular templates that was ported from the Angular compiler to Kotlin.
For Node.js-based TypeScript, JetBrains developed the Volar plugin to provide source maps inside the compiler. With the Go-based engine, it implemented a similar solution by porting parts of Volar to Kotlin and adapting them to the program's internal architecture. This mechanism combines the transpiled code and its maps, then translates IDE requests from the coordinates of the original code to the generated code seen by the compiler.
This approach enables coding assistance inside embedded Angular templates, but the post notes an important limitation: the TypeScript-Go content-mappers feature remains limited to files not written in TypeScript, and it appears that it will not support Angular use cases.
React Is Available Now, While Vue Remains in Development
For React, JetBrains says TypeScript 7 support is stable and ready for use, as the new engine works with coding assistance immediately after updating WebStorm and selecting TypeScript 7 in the preferences.
For Vue, JetBrains is working on porting the Vue adapter to Kotlin and Kolar, while continuing to assess whether the final integration will rely on the official content-mappers solution or on the Kotlin adapter and its associated architecture. Therefore, the post does not provide a final date for Vue support, while Angular integration continues to be improved alongside the development of the Angular compiler itself.
Why Does This News Matter?
The most important practical change is separating the performance gains of development tools from the constraints of upgrading TypeScript within the project. This may benefit teams working with large repositories or multi-package Angular projects, but the published figures represent JetBrains' test on Kibana and do not guarantee the same result for every codebase. Angular support also depends partly on WebStorm-specific integration solutions, making the development of TypeScript 7 support in the official Angular compiler a factor worth following.