Where new TypeScript work belongs
TypeScript Go was Microsoft's staging repository for the TypeScript 7.0 native port. Its README directs development and discussion to microsoft/TypeScript. The supplied repository metadata marks typescript-go archived and records its last push on August 31, 2026.
Use this checkout when a historical commit answers your question. For new contributions and reports, follow the repository's redirect. Readers evaluating the application package can turn to the existing TypeScript guide, which addresses a different task from reproducing this source checkout.
What happened when we ran it
Our October 9, 2026 sandbox run at commit 89d5d5b installed dependencies in 10 seconds, recording 437 dependencies and 453 MB on disk. Build failed with exit 1 after 3 seconds. Tests failed with exit 1 after 1 second. Neither command timed out.
The Hereby build task attempted go build '-tags=noembed' -o ./built/local/ ./cmd/tsgo. The test task attempted go test ./... '--timeout=45m'. Both log tails report spawn go ENOENT: the runner could not launch the Go executable. These are captured command attempts, not successfully executed examples or failed compiler assertions.
The run did not establish compiler correctness, application compatibility, editor behavior or throughput. Before investigating this checkout's behavior, make Go available to the source tasks and verify the actual executable versions. The recorded configuration was 3 CPUs, 8 GB RAM and image label lab-node:22; that label alone does not establish the runtime or operating-system version.
The repository scan recorded 136,830 files, approximately 5,668,799 source lines and 562.9 MB checked out. It detected monorepo workspaces and 3 CI workflow files, but no Dockerfile or tests directory. Those directory signals do not establish whether the project has tests; the captured task explicitly attempted Go tests.
Keep source setup separate from package instructions
The supplied README documents a packaged preview and says that for TypeScript 7.0 RC and later, the command name is tsc. Those package instructions are separate from the source tasks attempted in our sandbox. This review does not validate a published binary or infer its behavior from the source-command failures.
The README also retains a historical feature table that marks the API not ready and the language service in progress. Treat those as upstream status statements in the supplied document. They do not establish the current destination's API or compatibility. Tool authors should check the interfaces they need in the current project's documentation before building an integration.
Dependency advisories need their own investigation
npm audit reported 15 known vulnerabilities: 13 high and 2 moderate, with none critical or low. The supplied measurement does not identify affected packages or dependency paths, and it does not establish scan coverage.
Investigate those details before retaining the source environment. The audit summary does not prove that the compiler is exploitable or assess today's TypeScript package. It also does not explain the separate failure to launch Go.
Choose the destination for your task
The original TypeScript repository is the destination named for continued development and discussion. Its README documents the stable typescript package and ways to report bugs and contribute fixes. Start there for new TypeScript work; this review has not validated a current release against an application.
esbuild supports parsing TypeScript syntax and discarding type annotations. Its documentation says it does no type checking. Consider it when producing JavaScript bundles is the task, while retaining a separate type checker. We did not compare its performance with TypeScript Go.
What the documentation score covers
Documentation receives 3/5 under this rubric: 1 means basic orientation is missing; 2 means guidance has substantial gaps; 3 means useful guidance requires material interpretation; 4 means clear guidance has minor gaps; 5 means current instructions have been independently verified across the reviewed paths.
The README explains the move and provides a package entry point, but preview instructions, feature-status notes and future-tense closure wording remain below the closure notice. Readers must distinguish that historical material from current guidance. The score assesses the supplied documentation, not a successful setup.
Setup ease, community support and operational maturity remain unassessed. The unavailable Go executable prevented source validation; archival and a redirect do not measure current support responsiveness or compiler reliability.
For a historical investigation, establish a working environment at the recorded commit and rerun the relevant workload. For an application migration, compare representative diagnostics and generated output using the selected current package.