Automatically capture Angular errors alongside diagnostic reports and fix them for your users
Capture Angular errors and prioritize the ones that need fixing
Bugsnag for Angular is easy to install via npm or yarn. It only takes a few minutes to set up, and you'll immediately begin detecting errors. The library is incredibly small, has no external dependencies, and works in all browsers, including mobile. View the example project.
Bugsnag automatically alerts you via Slack and PagerDuty when errors are detected. Select your alerting preferences to know when new errors, regressions, or spike in your error rate occur.
Visibility into errors is only the first step. With two-way integrations and in-app workflow, you'll also make progress prioritizing bugs and moving them through your debugging process.
Pinpoint the root cause of errors so you can track and fix them efficiently
Bugsnag automatically captures a stacktrace with source code inline for easier debugging. Use sourcemaps with Bugsnag to get a fully readable stacktrace for every error.
Capture detailed information about the Angular-specific component and context where the error occurred.
See a timeline of user actions and events leading up to the error. Breadcrumbs can help you reproduce a bug and prove you've fixed it. You can even send additional breadcrumbs to your report.
Reproduce errors with important diagnostic data like browser and version, OS, request, and more. You can also send custom data unique to your application for even more detailed reports.
Thoughtfully built with front-end requirements in mind
Working at volume on the client side can make it hard to find the most important errors. Use Bugsnag's filters to search errors by user, version, browser, and more, and surface the errors most relevant to you.
Identify users alongside errors so you can see how widespread an error is. If it's really harmful, you can even reach out to your customers and proactively alert them of the fix.
Use the Releases dashboard to decide if a release is successful or needs to be rolled back. The crash rate indicator shows the percentage of sessions in a release that end in a crash, allowing you to compare release health and track improvements over time.
Cross-browser error grouping, domain whitelisting, discarding errors from legacy browsers, and stripped out browser extension errors help to decrease noisy Angular errors, and keep you focused on the ones that matter. Learn more JS monitoring best practices.
Resilient Angular error reporting that's used on some of the world's most popular apps including Airbnb, Pandora, and Eventbrite
Integrating with Bugsnag's lightweight Angular library does not result in any significant performance decreases.
Bugsnag error notifiers utilizes open source software so our users have visibility into the exception handling code. This allows the Bugsnag community to make pull requests for improvements.
Using 256-bit SSL, users of Bugsnag can send errors to our servers. Bugsnag can also be hosted on-premise for total data control.
Billy Pham
Technical Program Manager
Software Engineer, Chime
Nahuel Barrios
Engineering Manager
Antonio Niñirola
Engineering Manager