Jake Verbaten

Feel free to close as a breaking change, it would be nice to include the actual number of types in the error message next to maximum length though. I originally...

Fixed in the other issue.

I saw this again in the wild ``` fatal error: concurrent map read and map write goroutine 217682 [running]: internal/runtime/maps.fatal({0x10153c2b1?, 0x140968b1998?}) runtime/panic.go:1046 +0x20 github.com/microsoft/typescript-go/internal/ast.(*DiagnosticsCollection).GetDiagnosticsForFile(...) github.com/microsoft/typescript-go/internal/ast/diagnostic.go:159 github.com/microsoft/typescript-go/internal/checker.(*Checker).GetDiagnosticsWithoutCheck(...) github.com/microsoft/typescript-go/internal/checker/checker.go:13460 github.com/microsoft/typescript-go/internal/compiler.(*Program).getSemanticDiagnosticsForFileNotFilter(0x14010578380, {0x1019471f0, 0x101f6b620},...

I have not seen this issue recently, I switched over our team workflow to be a combination of `tsc` for building javascript and `tsgo` for Editor/IDE performance during development.

First exection ``` $ pnpm build:tsgo --stopBuildOnErrors  WARN  Unsupported engine: wanted: {"node":"^22.18.0"} (current: {"node":"v22.17.0","pnpm":"10.16.1"}) > [email protected] build:tsgo /Users/raynos/projects/depscan > tsgo -b --verbose --stopBuildOnErrors [11:23:58 AM] Projects in this build: *...

Not sure if this a real issue, the behavior feels non deterministic. I'm porting my monorepo from tsc => tsgo and reporting edgecases I'm running into in the process.

"noEmitOnError": true, It has no emit on error set. ``` { "extends": "../../tsconfig/tsconfig.strictest.json", "compilerOptions": { "lib": ["es2024", "dom", "dom.iterable"], "rootDir": "src", "outDir": "dist", "tsBuildInfoFile": "./dist/tsconfig.tsbuildinfo" }, "include": [ "src/**/*.js", "src/**/*.json",...