typescript-expert

This error comes from deeply recursive or circular types. Fix it by limiting recursion depth with conditional types, replacing type intersections with interfaces, splitting large union types, and breaking circular generic constraints.

Use Biome when speed is critical and you want one tool for linting and formatting with TypeScript-first support. Stay with ESLint when you need specific plugins, custom rules, type-aware linting, or Vue/Angular support.

Run tsc with --extendedDiagnostics to find bottlenecks, then enable skipLibCheck and incremental builds, tighten include/exclude patterns, and use project references with composite: true in monorepos.

This usually means moduleResolution does not match your bundler, baseUrl or paths are misaligned, or a stale cache exists. Check your tsconfig settings and clear node_modules/.cache and .tsbuildinfo files.

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

No, tsconfig paths only apply at compile time. For Node.js runtime, use ts-node with tsconfig-paths/register, an ESM loader alternative, or pre-compile with resolved paths for production.