Do not use `@ts-ignore`: it hides an error unconditionally and does not fail when the underlying error disappears. First inspect the diagnostic and fix the type, narrowing, generic constraint, or API declaration causing it. For example: ```ts function formatId(value: string | undefined): string { if (value === undefined) { throw new Error("id is required"); } return value; } ``` If a genuine, unavoidable third-party typing defect remains, use `@ts-expect-error` on the smallest line with a com...
Installs into .claude/skills of the current project.
Are you the author of Typescript Tooling?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-typescript-tooling-0f26a97a)
Do not use `@ts-ignore`: it hides an error unconditionally and does not fail when the underlying error disappears. First inspect the diagnostic and fix the type, narrowing, generic constraint, or API declaration causing it. For example:
```ts
function formatId(value: string | undefined): string {
if (value === undefined) {
throw new Error("id is required");
}
return value;
}
```
If a genuine, unavoidable third-party typing defect remains, use `@ts-expect-error` on the smallest line with a comment explaining the known issue; it becomes an error when no diagnostic is produced. Run the language diagnostics fallback plus `tsc --noEmit`, and do not disable strict checking or use `any` to mask the problem.
