ban-type-assertions

To ban unsafe type assertions in a TypeScript monorepo, enable the @typescript-eslint/consistent-type-assertions rule with assertionStyle set to never. This eliminates unsafe as type casts by enforcing compiler-verified type conversions across all packages.

The best way to replace TypeScript as type casts is using a tiered workflow: apply Zod parsing for external data, use control flow narrowing for union types, and add justified eslint disables for unavoidable edge cases to ensure runtime validation.

Enforcing consistent type assertions improves type safety by preventing type casts that bypass compiler checks. This eliminates runtime errors by ensuring all type conversions are verified by the compiler or validated via schema parsing libraries.

Yes, you can consolidate duplicate TypeScript schemas across multiple packages by promoting them to a shared common library. This reduces duplication, improves maintainability, and centralizes type management across distributed packages.

You should use eslint disables for unavoidable type assertions when replacing unsafe casts is not possible through Zod parsing or control flow narrowing. This handles edge cases while still enforcing the consistent-type-assertions rule across the codebase.

Banning type assertions works seamlessly with Zod for external data parsing by replacing unsafe casts with schema parsing. This ensures runtime validation of external data, satisfying requirements for compiler-verified type safety without manual type assertions.