Skip to main content

JavaScript crash reporting

Someone's browser threw an error you can't reproduce. The stack arrived anyway, mapped to your own line.

BugSplat listens to window.onerror and unhandled rejections, posts the error with its chain of causes, and resolves minified frames against your source maps. A few lines of code, any framework or none.

Why BugSplat for JavaScript

A few lines of code post every unhandled browser error, source-mapped to your files and lines, with the chain of causes that led there.

01 · It lands

Something breaks in your JavaScript build. You find out first.

Create a BugSplat client with your database, app, and version and wire it to window.onerror and unhandledrejection. Every unhandled error posts with its type, message, stack, and the chain of causes behind it. Angular, React, and Vue get their own integrations; everything else uses the client directly. If the site is the store or dashboard around a game, it reports into the same dashboard as the game.

  • Unhandled errors and rejections captured with a few lines, no framework required
  • Up to 100 linked causes per report, each with its own frames
  • Angular, React, and Vue integrations on the same client
A crash report in BugSplat with application, group, exception, platform, and the user's feedback - how JavaScript errors arrive

02 · It groups and resolves

A report count is not a bug count.

BugSplat groups JavaScript errors your way: your rules decide which call stacks count as the same bug, and the list is ranked by how many people each one hit. Minified stacks resolve against the source maps you upload with each release, so frames read as your own files and lines.

  • Thousands of reports collapse into a short list of distinct bugs
  • Your own file and line from the source map, not an offset into a minified bundle
  • OS, hardware, and build on every report
A symbolicated active thread in BugSplat with the faulting frame expanded to its file, line, arguments, and locals

03 · It tells you

Stay ahead of the next one.

Alerting for JavaScript errors hits Slack, Discord, or Teams the moment something spikes. Version-over-version analytics show whether each release is more stable than the last.

  • Regressions flagged when a fixed crash comes back
  • Daily and weekly digests with the highlights
A BugSplat new group alert in Discord with the crash group and stack trace

What makes BugSplat different

Built for native code. Works for the web around it.

The store, dashboard, and account pages around a native app land next to the app's crashes, with the same grouping, alerts, and trends.

Native from the start

BugSplat has been turning minidumps into readable stacks since 2005. Symbols, PDBs, and native crashes are the core of the product.

A bill that holds still

Flat monthly plans with fixed limits. A spike in crash volume after a release doesn't change your bill.

Answered by the people who build it

Email support with a JavaScript question and you'll hear back from an engineer who builds BugSplat, usually the same day.

JavaScript setup

Wire up JavaScript and read a real stack the same day.

Add the SDK and upload source maps with each build. If you get stuck, contact support and you'll reach the engineers who build BugSplat.

By clicking "Accept", you agree to the storing of cookies on your device. View our Privacy Policy .