For React
ErrorDock for React.
ErrorDock for React captures render errors through an error boundary component, attaches the React component stack alongside the JavaScript stack trace, and tracks feature usage through hooks so adoption data comes from the same SDK as your errors.
Component stacks, not just call stacks
A JavaScript stack trace tells you which function threw. The React component stack tells you where in the tree it was rendering, which is usually the more useful of the two when a render fails.
An error boundary that reports
Drop the provided boundary in and render errors are captured with props context and the component stack, rather than silently unmounting a subtree.
Feature usage from hooks
The useErrorDock hook records interactions and wraps a feature's work in withFeature, which records the outcome as well as the use. Feature health then shows that feature's adoption beside its error rate, so a bug in a component is read against how many people actually reach that component.
Related
- ErrorDock for JavaScript. Browser error monitoring with source map support, breadcrumbs and session context from one lightweight SDK.
- ErrorDock for React Native. JavaScript errors, sessions and screen tracking in React Native applications, with release and device context.
- React error monitoring. Error boundaries, component stacks, source maps and what React error monitoring actually needs to capture in production.
- Measure the features worth protecting. Track feature adoption and interactions beside technical health to understand which parts of your product deserve attention.
Bring your application into focus.
Tell us about your stack. We will help define the right beta setup for your first project.