debugger statement left in code
Part of Code Quality & Syntax, which counts for 20% 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
A `debugger;` breakpoint statement was left in source.
Why it matters
A debugger statement halts JavaScript execution whenever a user has devtools open, freezing the page mid-action. At best it is dead weight in the bundle; at worst it is a page-breaking pause that shipped because nobody re-read the diff.
How to fix it
Delete the statement. Enable the ESLint no-debugger rule (on by default in eslint:recommended) so CI catches new ones, and if you bundle with terser or esbuild, configure the production build to drop debugger statements as a backstop.
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