diagnostic · one of 36 free, no counter
Errors
Why is this page broken, and what exactly is failing?
A broken page usually says exactly what is wrong, to a console nobody has open. This is that console as a ledger: press record, reproduce the problem, and every uncaught error, unhandled rejection, CSP violation and failed resource load becomes a row - one row per distinct failure with a count on it, because an error thrown four hundred times in a loop is one fact, not four hundred lines to scroll.
Reach it Press ⌘ + K on any tab and type errors. Ctrl + K on Windows and Linux
in the panel · free, no counter
What this actually is
uncaught errors, rejections and blocked loads, counted liveA page that misbehaves for someone who cannot open devtools, a bug report that needs the actual error message rather than a description of the symptom, or a check that your own page stays quiet while it is used. Errors thrown before the listeners exist are gone, so record first and reproduce second.
Asked about this diagnostic
4 of themWhy does it need a record button?
Because errors thrown before the listeners exist are not recoverable, and a tool that pretended to read the past would be guessing. The honest surface is press record, reproduce, read - and the listeners are removed when you stop, leave the tool or close the panel.
Can an error message contain something sensitive?
It can, which is why every message passes the same sanitizer as everything else read from a page - emails and token-shaped strings are redacted, query strings are cut from source URLs - and stack traces are never kept at all. Nothing is stored and nothing is transmitted.
How is this different from Console?
Thrown against said. This hears what escaped - exceptions nothing caught, rejections nothing handled, loads that failed. Console taps what the page deliberately says with console.log and its siblings, warnings included. A React key warning shows up there, not here.
Why one row with a count instead of a log?
Because the failure mode of an error tool is an error loop: one bad interval can emit thousands of identical lines, and a log presents that as a wall. A distinct row with ×1,204 on it is the same fact stated once, and the rarer second error stays visible under it.
how to use errors
- Open Errors and press record before you reproduce anything.
- Reproduce the failure. Uncaught errors, rejections, CSP violations and failed loads all become rows.
- Stop and read: one row per distinct failure with a count, never a scrolling log.
- Copy the actual message into the bug report instead of a description of the symptom.
70 of these · no host permissions · three free audits