typescript-refactor

Refactor TypeScript by applying custom type guards, exhaustive switches with never, and narrowing chains to eliminate unsafe as-casts. Enforce discriminated unions and branded types to make invalid states unrepresentable and ensure safe type architecture.

Improve TypeScript compiler performance during refactoring by adopting patterns that avoid deep recursion and preferring interfaces over intersections. Apply modern idiomatic practices to reduce compilation overhead and maintain type safety.

Exhaustive checking with never works by ensuring all union members are handled in switch statements, using the never type to catch unhandled cases at compile time. It eliminates unsafe casts by enforcing complete type narrowing chains.

Yes, you can adopt modern TypeScript features like using, accessor, and const type parameters when refactoring older code. Apply these newer language features alongside satisfies to preserve literal precision and improve type architecture safely.

TypeScript refactoring breaks type safety when inconsistent patterns allow invalid states or unsafe casts. Prevent it by enforcing principled guidelines: use discriminated unions, custom type guards, exhaustive checks, and branded types to make invalid states unrepresentable.

Avoid type predicates when exhaustive switches or built-in narrowing chains suffice, as overuse can complicate type architecture. Prefer them for custom guards that eliminate unsafe as-casts, ensuring reliable narrowing without unnecessary complexity.