Fresh install
Never used Sentry? Start here.
- 1. Run Epure (compose or Cloud)
- 2. Install @sentry/browser
- 3. Init with the Epure DSN and verify
Browser · @sentry/browserError tracking for browser JS.
Install @sentry/browser and point dsn at your Epure host. Uncaught exceptions and unhandled rejections land as issues, with sourcemaps for readable frames.
Host up → install SDK → paste DSN → confirm a 202.
Install
1 SDK
Install @sentry/browser. Point dsn at Epure.
Protocol
envelope
Official Sentry wire. Exceptions persist; transactions discarded.
Setup
< 10 min
Host up → DSN → first issue the same sitting.
Cost
0 seats
Self-host is unlimited seats. Hardware bounds volume.
Start here
From zero, or from Sentry.
Same finish line: @sentry/browser pointing at your Epure DSN, first issue in the list.
Already on Sentry
Keep the SDK. Change the DSN.
- 1. Create an Epure project and copy the DSN
- 2. Replace only the dsn string in init
- 3. Set traces/replay/profile rates to 0
Docs for this stack
The fit
Epure is the error tracker for Browser.
Install @sentry/browser once. Point the DSN at Epure. No Sentry Cloud account required. Only the open SDK client.
Official SDK, no proprietary agent
Install @sentry/browser (or keep it if you already have Sentry). Point dsn at Epure.
Two containers, no cluster
Rust binary plus PostgreSQL 16, self-hosted under 200 MB. Cloud runs the same path at $24.
Issues you can finish
Grouping, releases, alerts, and soft-sampling on spikes. Triage without a seat tax.
What the browser hides
Client failures that escape local repro.
Epure groups browser exceptions and demangles the stacks once you upload sourcemaps.
Uncaught exceptions
Global handlers capture throws the UI never surfaces. One issue per fingerprint.
Unhandled rejections
Async failures from fetch and event handlers land as issues you can resolve once.
Minified stacks
Upload .map files via release artifacts. Frames demangle to your source paths.
CORS preflight
OPTIONS on ingest routes so browser SDKs can POST envelopes from the origin you ship.
Breadcrumbs
Console, click, and navigation crumbs stay on the event so you see the path to the throw.
Install path
Host. SDK. First issue.
New to Sentry or already on it. Same three moves. Official SDK in, DSN pointed at Epure, one test throw.
Run Epure
docker compose up locally (optional `.env` for ports), or open Cloud. Register, name a project, copy the DSN from setup or Settings → SDK connection.
Install @sentry/browser
Add the official Sentry SDK from your package manager. Epure speaks the Sentry wire, so there is no @epure/* client.
Init and verify
Call Sentry.init with the Epure DSN. Throw once (or captureException). Confirm 202 and an issue in the list.
Wire path
Install the SDK. Point the DSN.
Fresh install or DSN swap: same init shape. Disable product lines Epure discards.
Install @sentry/browser
Official Sentry client from the package registry. No @epure/* SDK.
Point dsn at Epure
Paste the project DSN from Settings. Fresh install and Sentry migrants use the same field.
Disable discarded lines
Set traces, replay, and profile sample rates to 0. Epure stores exceptions only.
1npm install @sentry/browser@7.120.0Why Epure
The tracker that fits how you already ship front ends.
Check the fit before you paste the DSN.
Official SDK, no proprietary agent
Install @sentry/browser (or keep it if you already have Sentry). Point dsn at Epure.
Two containers, no cluster
Rust binary plus PostgreSQL 16, self-hosted under 200 MB. Cloud runs the same path at $24.
Issues you can finish
Grouping, releases, alerts, and soft-sampling on spikes. Triage without a seat tax.
Honest scope
Exceptions and stacks. We skip replay, profiling, and transaction APM, and never claim 100% compatibility.
Readable JS/TS stacks
Upload sourcemaps via release files. Local frames stay useful after minify.
You own the data path
Self-host keeps stack traces on your Postgres. Cloud soft-samples instead of surprise invoices.
FAQ
Before you paste the Browser DSN.
Do I need an existing Sentry Cloud account?
No. Install @sentry/browser from the package registry, create an Epure project, paste the DSN, and capture. You need their open SDK client, never their SaaS. Quickstart.
I already use @sentry/browser. Do I rewrite?
No. Leave the SDK. Change only the dsn to your Epure host. Set traces/replay/profile sample rates to 0 so you don’t ship volume Epure discards. Self-host install if you still need compose.
What about transactions, replay, and profiling?
Epure is exception tracking. Transactions are discarded. Replay and profiling items are ignored. Disable those sample rates in init.
How long until I see the first browser issue?
With Docker warm and a DSN in env, most people land a 202 and an issue the same sitting. Persistence is async, so under normal load an issue appears in well under a second.
Which wire path does browser use?
Browser uses POST /api/{project_id}/envelope/ with CORS preflight. Fixture @sentry/browser 7.120.0 is E2E tested in this repo.
How do I fix CORS errors from the browser SDK?
Epure answers OPTIONS on ingest routes. Set Access-Control-Allow-Origin to the origin that serves your app (or your configured allowlist). If preflight fails, the SDK never POSTs the envelope. Check the DSN host matches the Epure origin you opened in the browser.
Do minified stacks demangle?
Yes for JS/TS. Upload .map files through release artifacts (Sentry CLI, Vite plugin, or CI). Frames then show original file, function, and line. Other languages stay on raw frames. Guide: source maps.
Point the browser SDK at Epure tonight.
Open the docs, compose up or Cloud, install the SDK, paste the DSN.
Apache 2.0 · official Sentry SDK · swap DSN