typescript-expert

This error comes from deeply recursive or circular generic types. Fix it by limiting recursion depth with conditional types, replacing type intersections with interfaces, or splitting large union types. The Skill includes concrete code patterns for each fix.

Enable skipLibCheck and incremental compilation, configure precise include/exclude patterns, and use project references with composite: true in monorepos. Run tsc --extendedDiagnostics to measure check time and identify bottlenecks.

Choose Biome when speed is critical and you want one tool for linting and formatting in a TypeScript-first project. Stay with ESLint when you need type-aware linting, custom rules, or Vue/Angular support, which Biome lacks.

Enable allowJs and checkJs in tsconfig, rename files gradually from .js to .ts, add types file by file, then enable strict mode flags one at a time. Tools like ts-migrate and typesync can automate parts of the process.

Module resolution failures usually come from a moduleResolution setting that mismatches your bundler, misaligned baseUrl and paths, or stale caches. Check tsconfig settings first, then clear node_modules/.cache and .tsbuildinfo files.

Use branded types for critical domain primitives like UserId or OrderId where mixing plain strings would cause bugs. They create nominal typing at compile time with zero runtime cost, preventing accidental argument swaps at API boundaries.