Production JavaScript reliability

Turn cryptic production errors into readable stack traces.

A practical, engineer-focused reference for capturing JavaScript errors across the browser, Node.js, and modern frameworks — then symbolicating them with accurate source maps and wiring the whole pipeline into your observability stack.

Error handling & boundaries Source maps & stack traces

in-depth guides

core tracks

Browser · Node · Build

full coverage

console

Uncaught TypeError: n is not a function
    at a.min.js:1:24190
    at a.min.js:1:9020

// after source-map symbolication
✓ TypeError: handler is not a function
    at CheckoutForm.submit (src/Checkout.tsx:42:7)
    at onClick (src/Button.tsx:18:5)

Two tracks, end to end

Start with a track, then follow the inline links into focused implementation guides.

Core JavaScript Error Handling & Boundaries

Capture errors at every layer — global interception, framework boundaries, Node.js process behavior, and observability SDKs — then route them to production telemetry.

Explore the track

Source Map Generation & Stack Trace Debugging

Generate accurate source maps, store them securely, and symbolicate minified stack traces — from bundler config through CI/CD upload and cross-browser normalization.

Explore the track

Start here

High-signal guides from across the library.

Observability Integrate Sentry, Datadog & OpenTelemetry Wire browser error-monitoring SDKs with sampling and PII scrubbing at the boundary. CI/CD Upload source maps from GitHub Actions A pipeline that uploads, validates, and strips maps keyed to the release commit. Build config Generate hidden source maps in Vite Keep stack traces symbolicated while keeping original source off the public CDN. Browser capture Why window.onerror misses cross-origin errors The opaque "Script error." message, and the crossorigin + CORS fix that resolves it. TypeScript Narrow unknown in catch clauses Handle catch (e: unknown) safely with type guards and a normalizing helper. Cross-browser Parse the Safari / WebKit stack format Handle JSC's header-less frames and 1-based columns when normalizing traces.

Using this site

How the guides are organized

Each track opens with an architectural overview, then branches into implementation guides and targeted troubleshooting recipes. Inline links connect related concepts so you can move from a symptom to its fix in a click or two.

How to use the code examples

Examples are operational patterns, not drop-in snippets. Adapt endpoint names, SDK calls, and build flags to your runtime — every block is copy-pasteable as a starting point.