Browser Monitoring
Errors
Unhandled errors and promise rejections become error beacons. Use captureException for handled failures you still want in Mydle.
Automatic capture
After mydle.init, the SDK listens for window.error and unhandledrejection. Each event emits a beacon with type: "error".
captureException
try {
await checkout();
} catch (error) {
mydle.captureException(error, { step: "checkout" });
throw error;
}Optional context is scrubbed for sensitive keys before queueing. See Privacy.
Payload
Error beacons include message and optional stack / source location fields. URLs and stacks redact common secret patterns. Every beacon has an opaque eventId for idempotent ingest.
Dashboard
Open /app/browser → JavaScript Errors for fingerprint groups, occurrences, and affected sessions. Empty means no error beacons — not a synthetic zero rate.
Limitations
- Source-map annotation is best-effort when maps are uploaded via the API; oversized or mismatched maps are skipped.
- Cross-origin script errors without CORS-friendly scripts may yield opaque messages.
- No minidumps or native crash reporting in this SDK.