Guide
React error monitoring.
Error monitoring in React means capturing render errors through error boundaries, recording the component stack alongside the JavaScript stack trace, and resolving minified production bundles back to original source through source maps.
Error boundaries and what they miss
An error boundary catches errors thrown during rendering, in lifecycle methods and in constructors below it. It does not catch errors in event handlers, asynchronous code, server rendering, or the boundary itself — which is why a boundary alone is not error monitoring.
Component stacks
React provides a component stack separate from the JavaScript stack trace. The JavaScript trace says which function threw; the component stack says where in the tree it was rendering. For render failures the second is usually more useful, and both should be captured.
Source maps in production
A production stack trace pointing at main.a83f2.js:1:284100 is not actionable. Source maps uploaded for each release, matched to it, are what make a trace readable — and keeping them out of the public bundle is what keeps your source private while doing it.
Where ErrorDock fits
ErrorDock provides a React SDK with an error boundary component, component stack capture and feature usage hooks. Source maps are uploaded per release to its artifacts endpoint with a server key; during the beta, source-map upload is enabled per organisation.
Related
- ErrorDock for React. Error boundaries, component stacks and feature usage tracking for React applications, from one SDK.
- ErrorDock for JavaScript. Browser error monitoring with source map support, breadcrumbs and session context from one lightweight SDK.
- What is error monitoring? Error monitoring is the practice of automatically capturing, grouping and prioritising exceptions from running software. A practical guide to how it works.
- Find the failure. Keep the context. Group exceptions into issues, inspect stack traces and breadcrumbs, and understand which users and releases are affected.
Bring your application into focus.
Tell us about your stack. We will help define the right beta setup for your first project.