typescript

Avoid `any` and `as` by using `unknown` instead, which requires explicit type validation before use. This prevents unsafe type assumptions and catches errors at development time rather than runtime.

Use discriminated unions with an explicit `type` field to narrow variants safely. This pattern lets TypeScript's type guard automatically refine the type based on the discriminant value, eliminating unsafe type assertions.

Use runtime validation libraries like valibot to check data at runtime and ensure it matches your TypeScript types. This bridges the gap between compile-time types and actual data, preventing type-related bugs in production.

Non-null assertions (`!`) bypass TypeScript's safety checks and hide potential null reference errors. Removing them forces explicit handling of nullable values, making your code more robust and easier to debug.

Yes, discriminated unions work across APIs, data models, and component props. This approach ensures type-safe handling of different response variants and prop combinations consistently throughout your codebase.