Error tracking for the stack you already run.
Eight language fixtures plus Next.js. Install the official Sentry SDK (or keep it), point the DSN at Epure. Docs linked on every guide.
- @sentry/browser
Browser (JavaScript)
Client-only SPAs and static sites. Express and Nest belong in the Node guide, Next.js in its own.
Open guide
React
Vue
Angular
Svelte
Vite / CRA
static HTML - @sentry/node
Node.js
Node APIs and workers. Browser SPAs belong in the Browser guide, Next.js in its own.
Open guide
Express
Fastify
NestJS
Koa
Hono
Node workers / CLIs - @sentry/nextjs
Next.js
Full Next.js apps (client + server + edge). Prefer this over separate Browser + Node packages.
Open guide
Next.js App RouterPages RouterRSC / server actionsroute handlersedge - sentry-sdk
Python
Python web and workers. Keep sentry-sdk (Django/Flask/FastAPI integrations still apply).
Open guide
Django
Flask
FastAPI
Starlette
Celery - sentry-go
Go
Go services and CLIs. Keep sentry-go; framework middleware still posts to the same DSN.
Open guide
net/http
Gin
Echochi
FiberGo workers - sentry-ruby
Ruby
Rails, Sinatra, Sidekiq. Keep sentry-ruby / sentry-rails; only the DSN host changes.
Open guide
Rails
Sinatra
Sidekiq
plain Ruby - sentry-php
PHP
Laravel, Symfony, Slim. Keep sentry-php; framework packages still work with an Epure DSN.
Open guide
Laravel
Symfony
Slim
Artisan / PHP CLI - sentry-java
Java
Spring and JVM services, Android excluded. Keep sentry-java; raw-frame grouping.
Open guide
Spring Boot
Quarkus
Micronaut
JVM servlets - Sentry
.NET
ASP.NET Core and .NET workers. Keep the Sentry NuGet package; only the DSN host changes.
Open guide
ASP.NET CoreMinimal APIs.NET workers
Same language, two surfaces? Instrument both (e.g. React SPA + Express API = Browser guide and Node guide, two inits, usually one Epure project).