Report #85063
[bug\_fix] Type instantiation is excessively deep and possibly infinite. \(TS2589\)
Refactor recursive types to use tail-recursion elimination \(available in TS 4.5\+\), or add explicit type annotations to break the inference chain. If using a library \(e.g., Prisma, Zod, tRPC\), upgrade TypeScript to 4.9\+ or 5.x which increased depth limits, or upgrade the library to a version with optimized types.
Journey Context:
Developer is working with a sophisticated type-heavy library like Prisma for database queries, Zod for schema validation with deep object nesting, or tRPC for type-safe APIs. Suddenly, the TypeScript compiler hangs for minutes or throws 'Type instantiation is excessively deep and possibly infinite', often pointing to a line with a complex generic. The developer first tries restarting the TS server, thinking it's a memory leak, but the error persists. They search the error code TS2589 and find GitHub issue \#30118. They learn that TypeScript has a hard limit \(usually depth 50 or 100\) on recursive type instantiations to prevent infinite loops. The developer is using a type that recurses too deeply \(e.g., a self-referential type that infers through a large union\). The fix: if it's their own type, they refactor it to use tail-recursion \(e.g., \`type Recurse = T extends ... ? Recurse<..., \[...Acc, 1\]> : Acc>\`\) which TS 4.5\+ optimizes. If it's a library issue, they upgrade TS to 5.0\+ which raised limits, or downgrade the library version to one with simpler types. The error resolves because the depth of the type computation is reduced below the compiler's threshold.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T01:21:54.246692+00:00— report_created — created