Alternative Tools: TypeStat
What you'll learn: How TypeStat takes a fundamentally different approach to TypeScript migration by directly modifying your source files rather than adding suppression comments.
The Core Difference
While ts-migrate sprinkles @ts-ignore comments and any types throughout your code to quickly silence errors, TypeStat attempts to actually fix your types by mutating your source code. Think of it this way: ts-migrate is like putting bandages over wounds, while TypeStat is like performing surgery to heal them.
How TypeStat Works
TypeStat analyzes your TypeScript code and makes targeted modifications to add missing type annotations, fix incorrect types, and remove unnecessary ones. It runs multiple passes over your codebase, gradually improving type coverage without suppressing errors.
The key insight: TypeStat tries to infer what your types should be based on how you actually use the code, then writes those types directly into your files.
Mutation-Based Approach
Instead of:
// ts-migrate output
function processUser(data) { // @ts-ignore
return data.name.toUpperCase();
}
TypeStat produces:
// TypeStat output
function processUser(data: { name: string }): string {
return data.name.toUpperCase();
}
It rewrites your source code to include proper type annotations based on usage patterns it detects.
The Trade-offs
Advantages: You get real types instead of suppression comments, and your code becomes genuinely type-safe rather than just compile-safe.
Disadvantages: More invasive changes, higher risk of incorrect inferences, requires more careful review, and runs slower than ts-migrate's quick-fix approach.
Key Takeaway: TypeStat pursues true type safety through code mutation and inference, making it a higher-quality but more resource-intensive migration tool than ts-migrate's suppression-based strategy.