Will It Vibe?TypeScript build errors ignored
Part of Testing & CI, which counts for 10% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
typescript.ignoreBuildErrors: true tells next build to succeed even when the project has type errors. Broken types then ship to production instead of failing the build, which is exactly when you want the build to stop.
Why it matters
typescript.ignoreBuildErrors: true makes next build succeed even when the code has type errors. The type checker is your last gate before shipping, so silencing it lets genuinely broken code reach production, and the errors it was catching pile up invisibly until something breaks at runtime.
How to fix it
Remove ignoreBuildErrors so type errors fail the build again, then fix the errors they surface. If a single third-party type is genuinely wrong, narrow the suppression to that line with an @ts-expect-error comment and an explanation rather than disabling checking for the whole project.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo