migrate-to-shoehorn

You can replace unsafe TypeScript `as` assertions in test files by migrating them to `@total-typescript/shoehorn` type-safe equivalents, converting eligible assertions batch by batch while preserving runtime behavior.

The best way to batch convert `as` type assertions for test modernization is discovering eligible assertions across files, mapping them to shoehorn equivalents, and performing per-file migrations to avoid manual edits.

Migrating TypeScript test assertions to type-safe narrowing improves compile-time correctness so your tests better reflect intended types, reducing errors that unsafe `as` assertions allow through.

Yes, you can migrate `as` assertions in a large codebase without changing existing test behavior by performing per-file conversions that map unsafe assertions to shoehorn equivalents while preserving runtime logic.

Migrating test assertions to shoehorn does not require manual edits for every file when using batch conversion, which discovers eligible `as` assertions and applies mappings automatically across test files.

You should not use shoehorn to replace `as` type assertions when your tests rely on intentional type widening or narrowing behavior that shoehorn's stricter type-safe equivalents would restrict at compile time.