News
Microsoft Gets 'Real' on Native TypeScript Remake
Microsoft is progressing on its effort to port the TypeScript compiler and language service from TypeScript/JavaScript to native Go code, a project aligned with the upcoming TypeScript 7.0 release.
The company says the native toolset is now stable enough for broad daily use in editors and for command-line type checking, while also outlining key compatibility changes and a roadmap shift that makes TypeScript 6.0 the last JavaScript-based release.
"We're excited to give some updates on where we are, and show you how 'real' the new TypeScript toolset is today," Daniel Rosenwasser, principal product manager, said today.
The initiative was first unveiled earlier this year as a performance-focused rewrite intended to remove the Node.js runtime dependency and deliver substantial improvements to build speed, editor responsiveness, and memory usage. By October, Microsoft had brought native previews into Visual Studio 2026 Insiders and made nightly packages and Visual Studio Code extensions available for early adopters. The latest announcement frames that preview period as having moved into a more broadly usable phase.
Native Language Service Now Covers Core Editing Features
Microsoft's Dec. 2 update says the Go-based language service is now "fast, stable, and easy to use today -- including in your editor," and can be tried through a daily-updated VS Code marketplace extension.
[Click on image for larger view.] VS Code Extension (source: Microsoft).
The team reports parity across a wide set of editor capabilities, including completions, go-to-definition/type-definition/implementation, hover tooltips, signature help, formatting, selection ranges, code lenses, call hierarchy, document symbols, and quick fixes for missing imports.
Microsoft also says it has filled in previously missing features that blocked practical adoption of the preview, including auto-import completions, find-all-references, and rename. The company describes internal architectural changes intended to improve reliability while taking advantage of shared-memory parallelism, noting that early testers tolerated some instability in exchange for speed but that the system is now more robust across both small and large projects.
Compiler Parity Near Complete, With Build Mode Support
On the command-line side, Microsoft continues to ship nightly native preview builds that expose a tsgo CLI, designed to run alongside the existing tsc command. The company says TypeScript 7's type-checking is "very nearly complete," citing a large internal test suite where remaining mismatches are down to known incomplete work or intentional behavior changes. The update concludes that developers can already use TypeScript 7 to type-check projects for errors.
The native compiler also now supports key project-scale build workflows. Microsoft calls out support for incremental compilation, project references, and build mode, enabling many teams to swap in tsgo for faster checks and builds without reworking their configuration.
New benchmarks in the Dec. 2 post continue to show major performance gains. Across large repositories, Microsoft reports full-build speedups generally in the 7x to 10x range when comparing tsgo to tsc, with corresponding reductions in time-to-feedback for type checking.
Compatibility Changes: Deprecations, Defaults, and Remaining Gaps
Microsoft lays out a list of expected differences between the native TypeScript 7 line and the current JavaScript-based toolchain. Some are framed as temporary gaps to be closed before release, while others represent longer-term platform decisions.
As part of the TypeScript 6.0 bridge release and the TypeScript 7.0 native line, Microsoft highlights several deprecations and default shifts. These include enabling strict mode by default, defaulting the compilation target to the latest stable ECMAScript version, removing es5 targeting in favor of es2015 as a minimum, removing baseUrl, and removing node10 module resolution in favor of bundler and nodenext. An experimental ts5to6 tool is available to automatically update some tsconfig.json settings, currently limited to baseUrl and rootDir transformations.
Microsoft also flags remaining native gaps. JavaScript emit is not fully ported, and downlevel compilation currently only extends back to es2021 with no decorator emit support. Full es2015 targeting is planned but not finished. Watch mode exists but may be less efficient in some cases. Another major limitation is that TypeScript 7 does not support the legacy Strada API, which many third-party tools depend on. Microsoft is building a replacement Corsa API, but until that work is complete, existing linters, formatters, and extensions tied to the old API will not work directly with the native toolset.
JavaScript type checking and JSDoc handling have also been rewritten. Microsoft says this work intentionally drops some tags and relaxed rules, including no longer recognizing @enum and @constructor, which could surface new errors in some JavaScript projects.
Roadmap Shift: TypeScript 6.0 Is the Last JavaScript Release
The most consequential planning change in the Dec. 2 announcement is Microsoft's decision to treat TypeScript 6.0 as the final release based on the existing TypeScript/JavaScript codebase. The company says there will be no TypeScript 6.1, and only selective 6.0 patch updates for security issues, high-severity regressions, or critical compatibility fixes.
Microsoft positions TypeScript 6.0 as a compatibility-focused bridge from the 5.9 line to native 7.0, keeping type-checking behavior close to the existing toolchain while introducing deprecations that smooth the eventual transition. With the bridge defined, the TypeScript team says its main focus is now on closing remaining native gaps ahead of a full TypeScript 7.0 launch.
In another sign of the architectural reset, Microsoft says it will close and refresh existing language service issues tied to the old TSServer protocol, because the native language service uses the Language Server Protocol and a substantially rewritten implementation. Developers are asked to retry issues against the nightly native extension and file new reports where needed.
What Developers Can Do Now
Microsoft's guidance is that developers can already install the native preview VS Code extension and try the nightly native preview package for faster type-checking and builds, while keeping TypeScript 6.0 available for tooling that still depends on Strada APIs or for emit scenarios that tsgo does not yet cover. The update frames the native experience as ready for much broader real-world testing, with correctness and speed now at a point where most everyday TypeScript workflows can be exercised directly on the new toolchain.
About the Author
David Ramel is an editor and writer at Converge 360.