Post

On a codebase at work, it went from : 20s, 0 error on tsc To 5s, 1674 new errors on tsgo On a codebase about 1m loc Now, I have to figure out if they are real errors or false negative 😅 (the full codebase is in ts yet, some legacy are still js/jsx)

All stages; the embarassingly parallel stuff is more than 10x, checking is about 10x and we do it concurrently by spawning multiple checkers. The editor stuff is harder to measure but we're now able to do more than one thing at once, so it feels a lot better too.

I’m seeing runtime panics when trying to test against my repo (slice bounds out of range). Any debugging tips for trying to get a small repro so I can open an issue? The repo is large (1.5m lines of TS).

The build we publish is missing debugging information (for size reasons); the easiest thing to do is to clone typescript-go from source, then debug it there. From there, you should be able to add a launch task to run a Go program (the Go extension comes with some templates) to run ./cmd/tsgo.

Of course, best thing would be to file an issue now (even without the repro) as the backtrace is likely to help. Better still if you can provide the code!

It is amazing that this is happening. That said, just tried the native preview and we get 30036 errors in 2549 files, in 20s (down from 1m:45s with tsc 5.8) 😭 Will keep checking on the progress as it gets closer to the behavior of the existing compiler.

Status update on this: with the latest native preview and a few changes (mostly actual bug fixes) on our side, we managed to get it building our whole codebase in ~16s. That’s down from ~1m:40s with tsc 🤯🎉