See the errors your users hit, in your own source.
Browser code fails on devices you will never touch, in a minified bundle you cannot read. bughq captures the throw, resolves it back to your original file with a source map, and folds every occurrence into one issue.
import { bughq } from '@bughq/sdk'
bughq.init({
key: 'bughq_3c88ef2b5b7c42a9963792eaee64754d',
release: 'web@2.14.0',
environment: 'production',
})
// unhandled rejections and window.onerror are captured
// automatically, with the user action that led up to themHow frontend teams use it
01
Ship the source map with the build
Your bundler already emits a source map. Upload it on deploy and every frame in every trace points back to the real file, function, and line.
02
Errors group across browsers and devices
The same TypeError from Chrome, Safari, and an in-app webview folds into one issue with a device and browser breakdown, not six near-duplicates.
03
A regression names its release
Each event carries the release it came from, so a spike after a deploy points straight at the build that introduced it.
Your source
Source maps turn minified frames back into the code you wrote.
SPA-aware
History navigations, async rejections, and event handlers are all captured.
Per device
Every issue breaks down by browser, OS, and release automatically.