APM, error tracking, and dashboards for modern web apps. Ten-minute setup, transparent flat pricing, and support from engineers who actually use the product. Learn more →
Typescript-go Alternatives
Similar projects and alternatives to typescript-go
-
-
AppSignal
Monitoring that respects your time & budget. APM, error tracking, and dashboards for modern web apps. Ten-minute setup, transparent flat pricing, and support from engineers who actually use the product.
-
-
-
llvm-project
The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
-
swift-evolution
This maintains proposals for changes and user-visible enhancements to the Swift Programming Language.
-
-
biome
A toolchain for web projects, aimed to provide functionalities to maintain them. Biome offers formatter and linter, usable via CLI and LSP.
-
-
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
typescript-go discussion
typescript-go reviews and mentions
-
Rust Port of TypeScript (Tsc)
I suppose my comment sort of implies this. I think the naive knee jerk reaction is that if you can spit out perfect machine level code against a specification, then logically being closer to bare metal would help with performance. However, without knowing the details of how things worked it is though to say whether it is truly "reasonable" or not.
But more importantly, the Typescript team themselves [1] picked Golang mostly out of ergonomics and ease of porting at the time. It is becoming more increasingly more to "taste" what ergonomics means. Notably, they did not pick it because they believed it to be the fastest option. But speed was on the mind, giving way to ergonomics and ease of porting. At least, this is my read.
[1] https://github.com/microsoft/typescript-go/discussions/411
-
TypeScript 7 Went Native: What Actually Changes And What Doesn't
This wasn't luck. It's the reason the team chose Go in the first place. The existing compiler is a decade of accumulated behavior: pointer-heavy tree traversals, shared mutable state, thousands of subtle decisions encoded in its structure. The team explicitly framed the project as a port, not a rewrite, translating the existing codebase nearly function-for-function to preserve its exact behavior. Go won because idiomatic Go could mirror the existing code's shape; a Rust version would've forced them to rethink memory and mutation from scratch, turning a port into a rewrite and a compatibility promise into a prayer.
-
How is the Bun Rewrite in Rust going?
What's taken 1:1, deliberately, is the compiler core. That was almost perfectly 50% of the non-test code.
However open the codebases side-by-side and you'll quickly see even those parts aren't as 1:1 as that would naively imply:
https://github.com/microsoft/typescript-go/tree/main/interna...
https://raw.githubusercontent.com/microsoft/TypeScript/refs/...
(The TS file is 3MB and github won't display it inline)
-
TypeScript 7
> this TS migration started long before AI was able to help
Yes, but that doesn't mean it wasn't also "helped" along by AI.
See:
1. https://github.com/microsoft/typescript-go/pull/1387
2. https://github.com/microsoft/typescript-go/pull/2978
3. https://github.com/microsoft/typescript-go/pull/1138
4. etc...
Copilot is the "user" with the 2nd most commits (and the 15th and 19th too), and that's just what's been tracked in git.
---
The initial port was automated, then devs got in there, then LLMs got in there.
-
Why TypeScript 7.0 Was Rewritten in Go
The entire article is speculative rubbish. The real answer was posted in the official repo: https://github.com/microsoft/typescript-go/discussions/411 Why would trust anything else?
-
TypeScript 7 RC: the compiler rewritten in Go, around 10x faster
TypeScript 7 doesn't touch your code or the typing rules, it goes after speed, both in the build and in the editor. The sensible plan: move to TypeScript 6 now to clear the warnings, test the RC in parallel on a real project, and report bugs on the microsoft/typescript-go repo. Stable lands next month.
-
tsgo: qué cambia en el compilador TypeScript reescrito en Go y qué significa para proyectos reales
# Ejemplo de job paralelo en GitHub Actions para evaluar tsgo # Sin tocar el build principal jobs: typecheck-experimental: runs-on: ubuntu-latest continue-on-error: true # no bloquea el pipeline si tsgo falla steps: - uses: actions/checkout@v4 - name: Instalar Go uses: actions/setup-go@v5 with: go-version: '1.22' - name: Clonar y compilar tsgo run: | git clone https://github.com/microsoft/typescript-go /tmp/tsgo cd /tmp/tsgo && go build ./cmd/tsgo - name: Medir time-check con tsgo run: | time /tmp/tsgo/tsgo --project tsconfig.json - name: Medir time-check con tsc (para comparar) run: | time pnpm tsc --noEmit
-
TypeScript 7.0 Beta
A quote from the official FAQ - https://github.com/microsoft/typescript-go/discussions/411:
>By far the most important aspect is that we need to keep the new codebase as compatible as possible, both in terms of semantics and in terms of code structure. We expect to maintain both codebases for quite some time going forward. Languages that allow for a structurally similar codebase offer a significant boon for anyone making code changes because we can easily port changes between the two codebases. In contrast, languages that require fundamental rethinking of memory management, mutation, data structuring, polymorphism, laziness, etc., might be a better fit for a ground-up rewrite, but we're undertaking this more as a port that maintains the existing behavior and critical optimizations we've built into the language. Idiomatic Go strongly resembles the existing coding patterns of the TypeScript codebase, which makes this porting effort much more tractable.
-
TypeScript 6.0
Can't wait for tsgo to be generally available and supported. It's what, at least a quarter or maybe 2 quarters away?
Also here's a discussion I always like reading: Why Go? https://github.com/microsoft/typescript-go/discussions/411
- oxlint-tailwindcss: el plugin de linting que Tailwind v4 necesitaba
-
A note from our sponsor - AppSignal
www.appsignal.com | 9 Oct 2026
Stats
microsoft/typescript-go is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of typescript-go is Go.