Server and clientOne Nitro hook catches every server path; a browser plugin catches the rest, including after hydration.
Traces resolved to sourceThe failing line in context. Maps are read from disk, never served to the public.
Broken downBrowser, OS, device, release, route, session — what the occurrences have in common, measured against real traffic.
The bodies, not just the stackWhat came back, and what was sent if you ask for it. A stack says where the code broke; a body says what broke it.
Never the reason you are downWrites are batched off the request path. If the database cannot be opened, collection stops and the app keeps serving.