@ts-ignore is almost always the worst option

"Sometimes, I want to ignore a TypeScript error without doing a proper fix. Maybe I'm prototyping and don't need perfect type safety. Maybe TypeScript isn't smart enough to understand a necessary workaround. Or maybe I'm unable to figure out a solution because I'm not a TypeScript expert!"

"@ts-ignore tells TypeScript to ignore the next line. @ts-expect-error asks TypeScript to ignore the error on the next line. If there is no error, TypeScript will tell you that you should remove the comment-in other words, it's a waste. Both directives work the same way when there's an error, ignoring the problem: However, they work differently when there isn't an error. Where @ts-ignore ignores the next line, @ts-expect-error complains that it's unnecessary."

Using // @ts-ignore suppresses all TypeScript errors on the following line and can hide legitimate problems. @ts-expect-error suppresses an expected error but produces a diagnostic if no error exists, preventing stale or unnecessary comments. @ts-expect-error thus encourages removal of obsolete ignores and reduces silent masking of issues. The any type can be used tactically to limit the scope of type-suppression while retaining clearer intent. Quick editor-suggested fixes like @ts-ignore are convenient for prototyping but risk long-term code quality problems.

Read at Evanhahn