typescript

To enforce strict TypeScript patterns during refactoring, apply const-based constant collections, derive types from them, use flat one-level interfaces, and replace any with unknown. This standardizes type safety and reduces runtime errors across .ts and .tsx modules.

Handling unknown types instead of any in TypeScript involves favoring unknown for flexible APIs and using generics. This preserves type safety while allowing dynamic data handling without bypassing the compiler's strict type checks.

Structuring clean TypeScript interfaces requires keeping them flat at one level deep. Separate nested inline objects into distinct interfaces to clearly define data shapes, which improves maintainability and prevents accidental type mismatches.

You can use this to refactor .tsx files as well as standard TypeScript files. It targets both .ts and .tsx codebases to enforce strict type patterns, safe generic usage, and proper unknown handling during feature development.

You need a standard TypeScript toolchain setup including Node.js, npm or yarn, and TypeScript installed in your project. This environment is required to validate and apply the strict type rules and best practices.

Using utility types like Pick, Omit, Partial, and Readonly instead of custom interfaces provides concise and expressive type definitions. They enable safe type derivations from existing shapes, reducing boilerplate and preventing type duplication errors.