typescript-expert

This error comes from deeply recursive or circular generic types. Limit recursion depth with conditional types, replace type intersections with interfaces, split large union types, and use type aliases to break recursion cycles.

Enable allowJs and checkJs in tsconfig, then rename files from .js to .ts gradually while adding types file by file. Enable strict mode flags one at a time, and use tools like ts-migrate or typesync to automate parts of the process.

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, specific plugins, or Vue/Angular support.

Check that moduleResolution matches your bundler, verify baseUrl and paths alignment, and confirm workspace protocol usage in monorepos. Clearing caches like node_modules/.cache and .tsbuildinfo often resolves stale resolution state.

No, tsconfig paths only apply at compile time. For runtime resolution use ts-node with tsconfig-paths/register, ESM loaders, or pre-compile with resolved paths for production builds.

Enable skipLibCheck and incremental compilation, configure precise include/exclude patterns, and use project references with composite: true in monorepos. Diagnose bottlenecks with tsc --extendedDiagnostics or --generateTrace.