TypeScript compilation produces no errors

Every @ts-ignore comment suppresses a real type error — it does not fix the underlying type mismatch, it hides it. The bug still exists at runtime; TypeScript just stops warning about it. Three or more suppressions signal a pattern of bypassing the type system rather than fixing it, which compounds: developers learn that @ts-ignore is an acceptable solution, and the count grows. ISO 25010 maintainability.modifiability degrades because refactoring becomes unpredictable — suppressions hide which code actually works.

Find every suppression in application source files:

grep -r "@ts-ignore\|@ts-nocheck" src/

For each one: if it suppresses a genuine type error in your code, fix the underlying type. If it works around a bad type from a third-party library, use a specific cast (value as SpecificType) rather than suppressing the whole line. Prevent new suppressions with:

"@typescript-eslint/ban-ts-comment": ["error", { "ts-ignore": "allow-with-description" }]

This forces every remaining suppression to include a comment explaining why it exists.