Fresh install
Never used Sentry? Start here.
- 1. Compose up on your host
- 2. Install @sentry/react
- 3. Init with the Epure DSN and verify
ReactError tracking for React with @sentry/react
Use this page when you wrap a React tree in Sentry.ErrorBoundary. Use /integrations/browser for vanilla JS, Vue, Angular, Svelte, and static HTML. Pin @sentry/react@7.120.0. Set traces, profiles, and replay sample rates to 0. Throw in render, confirm HTTP 202, then an issue row.
Host up → install SDK → paste DSN (project id from Settings → SDK connection) → confirm a 202.
Start here
From zero, or from Sentry.
Same finish line: @sentry/react 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 React.
Install @sentry/react once. Point the DSN at Epure. No Sentry Cloud account required. Only the open SDK client.
Official SDK, no proprietary agent
Install @sentry/react (or keep it if you already have Sentry). Point dsn at Epure.
Self-host without a broker fleet
Postgres holds issues and events. No Kafka or Redis in the OSS compose. Self-host is a $0 software license; you still run the host. Cloud Pro is $24 and Plus is $79.
Issues you can finish
Grouping, releases, alerts, and soft-sampling on spikes. Triage without a seat tax.
What the boundary catches
Render throws that never reach a window handler.
Sentry.ErrorBoundary reports React render failures. The browser page stays vanilla JS.
Sentry.ErrorBoundary
Wrap the tree once. Render throws inside the boundary become one issue per fingerprint.
Render throws
A component that throws during render is the check. Mount it under the boundary and send once.
Event handlers
Click and submit handlers are outside the boundary. Call captureException in those catch paths.
Browser CORS
The SDK still posts from the page origin. OPTIONS has to succeed before the envelope leaves the tab.
Minified component stacks
Upload JS/TS maps for the same release when the production bundle is minified.
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). Register, name a project, copy the DSN from setup or Settings → SDK connection. Self-host is the path that ships today.
Install @sentry/react
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
Init @sentry/react. Wrap the tree.
Call init once, then put Sentry.ErrorBoundary around the tree. Sample rates stay at 0.
Install @sentry/react
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/react@7.120.0Why Epure
Install @sentry/react. Point the DSN. Verify.
Keep the official SDK. Change only the host.
Official SDK, no proprietary agent
Install @sentry/react (or keep it if you already have Sentry). Point dsn at Epure.
Self-host without a broker fleet
Postgres holds issues and events. No Kafka or Redis in the OSS compose. Self-host is a $0 software license; you still run the host. Cloud Pro is $24 and Plus is $79.
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 React DSN.
Do I need an existing Sentry Cloud account?
No. Install @sentry/react 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/react. 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 React 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 React use?
Browser envelope POST /api/{project_id}/envelope/ with CORS. CI live smoke names @sentry/browser 7.120.0. This page is the React boundary setup. The install pin @sentry/react@7.120.0 matches that JavaScript line.
How do I verify the first React issue?
Throw during render inside Sentry.ErrorBoundary (event handlers need captureException). Expect HTTP 202, then an issue row. Verify. A rejected DSN: Invalid DSN. A 202 with an empty list: Events not showing. Epure stores exceptions. No session replay, distributed tracing, profiling, or logs.
Point React at Epure tonight.
Compose up. Install @sentry/react. Wrap the tree.
Apache 2.0 · official Sentry SDK · swap DSN