expert-typescript-programmer

To refactor TypeScript code for strict types, update your tsconfig module settings, apply explicit inputs and outputs, replace 'any' with generics or discriminated unions, and use import type and satisfies to maintain strong type contracts.

Reviewing public APIs in TypeScript involves preserving compatibility by aligning exports with package boundaries, applying type guards, and ensuring strong type contracts using explicit types and discriminated unions across your .ts and .tsx files.

You need type guards and discriminated unions in a Remix codebase when runtime contracts must be strictly enforced, ensuring that evolving APIs and module settings do not introduce subtle regressions or type-safety gaps.

Yes, this type-safety approach works directly with your existing tsconfig and module settings, applying strict typing rules across .ts and .tsx files to enforce runtime contracts and eliminate type assertions within the Remix repo.

Using 'any' in TypeScript leads to maintenance headaches because it bypasses the compiler's type checking, preventing the enforcement of runtime contracts and causing subtle regressions when public APIs or module settings evolve.

Relying on type assertions limits type-safety by overriding the compiler rather than enforcing strict runtime contracts, which increases the risk of bugs and API regressions compared to using explicit types, generics, and the satisfies operator.