What is this?
This was the staging repo for TypeScript 7.0 — a native port of the TypeScript compiler written in Go. The port is finished, so the repo is closed and development has moved back to the original microsoft/TypeScript repository.
This was the staging repo for TypeScript 7.0 — a native port of the TypeScript compiler written in Go. The port is finished, so the repo is closed and development has moved back to the original microsoft/TypeScript repository.Is this a fork of TypeScript or a rewrite?A rewrite: the whole compiler — parsing, type checking, emit, watch and build modes — reimplemented in Go instead of the original JavaScript codebase. Long-term the plan was always to merge it back into microsoft/TypeScript, which is what has now happened.
A rewrite: the whole compiler — parsing, type checking, emit, watch and build modes — reimplemented in Go instead of the original JavaScript codebase. Long-term the plan was always to merge it back into microsoft/TypeScript, which is what has now happened.How do I get it running?The preview shipped on npm as @typescript/native-preview — install it and run tsc (the command name for TypeScript 7.0 RC and later). There was also a preview VS Code extension on the marketplace. Since the port completed, current releases come from microsoft/TypeScript.
The preview shipped on npm as @typescript/native-preview — install it and run tsc (the command name for TypeScript 7.0 RC and later). There was also a preview VS Code extension on the marketplace. Since the port completed, current releases come from microsoft/TypeScript.Do I need Node installed to use it?No — the compiler is a native Go binary, so running it needs nothing beyond installing the npm package. Building this repo from source is different: it is an npm workspace requiring Node 20.19+ and the hereby task runner.
No — the compiler is a native Go binary, so running it needs nothing beyond installing the npm package. Building this repo from source is different: it is an npm workspace requiring Node 20.19+ and the hereby task runner.Is this repo the one I should use now?No — it is closed and will be permanently archived in September 2026. Development and discussion, including issues, happen in the original microsoft/TypeScript repository.
No — it is closed and will be permanently archived in September 2026. Development and discussion, including issues, happen in the original microsoft/TypeScript repository.How close is the Go compiler to the TypeScript 6 we use today?By the repo's status table, program creation, parsing, tsconfig handling, type resolution, type checking, JSX, emit, watch mode, project references and incremental builds are all done — type checking reports the same errors, locations and messages as TS 6.0. The language service was still in progress and the compiler API was not ready.
By the repo's status table, program creation, parsing, tsconfig handling, type resolution, type checking, JSX, emit, watch mode, project references and incremental builds are all done — type checking reports the same errors, locations and messages as TS 6.0. The language service was still in progress and the compiler API was not ready.Is there a VS Code extension for it?Yes — a preview extension was published on the VS Code marketplace, enabled through a setting in your VS Code configuration. It works alongside the @typescript/native-preview compiler.
Yes — a preview extension was published on the VS Code marketplace, enabled through a setting in your VS Code configuration. It works alongside the @typescript/native-preview compiler.Does it handle plain JavaScript and JSX?Yes. JSX is done, and JavaScript-specific inference and JSDoc are complete — though some JS features are intentionally missing, and JS declaration emit intentionally differs to be closer to TS declaration style.
Yes. JSX is done, and JavaScript-specific inference and JSDoc are complete — though some JS features are intentionally missing, and JS declaration emit intentionally differs to be closer to TS declaration style.Why rewrite the compiler in Go at all?The README does not spell out the motivation — it points to the TypeScript 7 announcement post for background. This repo was simply the staging ground for that native port while it was under development.
The README does not spell out the motivation — it points to the TypeScript 7 announcement post for background. This repo was simply the staging ground for that native port while it was under development.What are similar projects?TypeScript, pyright, prepack, tools, vscode-extension-samples, esbuild, graphiql, YouCompleteMe
TypeScript, pyright, prepack, tools, vscode-extension-samples, esbuild, graphiql, YouCompleteMeWhich topics is it in?typechecker, language-server-protocol, vscode-extension, microsoft, compiler, deprecated, performance, go, npm, apache-2.0, typescript, javascript
typechecker, language-server-protocol, vscode-extension, microsoft, compiler, deprecated, performance, go, npm, apache-2.0, typescript, javascript