clean-typescript

To improve TypeScript code quality, prefer type aliases for most situations and use interfaces for public, extensible object shapes. This keeps types small and composable while enforcing correctness and maintainability.

Handle null and undefined in TypeScript by using explicit guards and avoiding non-null assertions as regular practice. This enforces null safety and improves overall correctness across app-scale projects.

Yes, prefer explicit return types for public functions in TypeScript. This enforces correct public API design, prevents unintended type changes, and improves maintainability across app-scale projects.

Use interfaces in TypeScript when defining public, extensible object shapes. For most other situations, prefer type aliases to keep your types small, composable, and focused on correctness over ceremony.

Yes, this TypeScript refactoring approach targets developers writing code in app-scale projects. It guides type declarations, function design, nullability, and error handling to improve maintainability across large codebases.

Avoid non-null assertions in TypeScript because relying on them bypasses the compiler's null safety checks. Using explicit guards instead enforces correctness and prevents runtime errors in your codebase.