Sentry JavaScript SDKs
https://github.com/getsentry/sentry-javascript- Category
- Developer Tools
- Rank
- No. 242Tools index
- Pricing
- Open Source
- Type
- TOOL
- Builder
- getsentry
- GitHub
- 8.7k stars
- Latest release
- 11.0.0-beta.1
- Date
About
Official Sentry SDKs for JavaScript runtimes — browser, Node.js, edge, React, Next.js, Svelte, and more, with sourcemap-aware stack traces.
What it does
It adds runtime reporting and instrumentation to JavaScript applications. Developers install a platform-specific package, configure a Sentry connection, then capture messages, exceptions, sessions, traces, metrics, logs, feedback, and check-ins through a common model.
Why it's ranked here
The project combines unusually broad framework coverage with platform-specific entry points and a shared core. Its exports cover error capture, tracing, logging, metrics, session replay, profiling, feature flags, databases, web frameworks, and AI tooling. That breadth makes it a strong default when one application spans several JavaScript environments.
What's good
The platform packages share core types and capabilities while adding native framework hooks. React includes error boundaries, profiling, Redux, and router support. Node exposes integrations for major servers, databases, queues, loggers, feature flags, and AI libraries. Dedicated packages also address serverless platforms, edge runtimes, Bun, Deno, and WebAssembly.
Tradeoffs
The package surface is large, so teams must choose the correct high-level SDK and consult its specific instructions. Some capabilities remain less mature, with Effect explicitly marked alpha. Support for older versions depends on community demand and usage rather than an unconditional maintenance window. Native Electron, React Native, and Capacitor support lives in separate repositories.
How to use it well
Use it when production JavaScript spans browsers, servers, frameworks, serverless functions, or edge runtimes and needs consistent runtime telemetry. Start with the high-level package matching each deployment target, then add only the relevant integrations. Treat it as application instrumentation, not a replacement for automated tests or framework-specific debugging tools.
Technical notes+
The root package.json defines a private Yarn workspace monorepo orchestrated by Nx, with separate transpilation, type, bundle, lint, size-limit, unit, integration, and end-to-end tasks. packages/core/src/index.ts aggregates shared, server, and browser exports, while packages/core/src/server.ts deliberately excludes strictly browser-specific code. packages/core/server.js provides a CommonJS compatibility shim for bundlers that cannot resolve package subpath exports. Platform barrels such as packages/node/src/index.ts, packages/bun/src/index.ts, packages/deno/src/index.ts, packages/react/src/index.ts, and packages/vue/src/index.ts re-export shared capabilities and add runtime-specific integrations. packages/wasm/src/index.ts patches streaming WebAssembly compilation, attaches debug images to events, rewrites matching frames for server-side symbolication, and forwards worker images to the parent thread. packages/hono/src/index.ts is currently an empty export.
Observed
- Primary language
- TypeScript, with a small JavaScript compatibility shim shown
- Packaging
- Private Yarn workspace monorepo containing public packages under the Sentry namespace
- Install surface
- High-level SDK packages install through npm or Yarn
- Interface
- JavaScript and TypeScript libraries with platform-specific entry points
- Platform support
- Browsers, Node, major UI frameworks, server frameworks, serverless platforms, Bun, Deno, Cloudflare, and WebAssembly
- Build structure
- Nx coordinates transpilation, type generation, bundling, linting, size checks, and tests
- Testing structure
- Dedicated browser, Node, Bun, Deno, Cloudflare, bundler, and end-to-end integration workspaces
Read from README.md, package.json, packages/core/server.js, packages/bun/src/index.ts, packages/vue/src/index.ts, packages/core/src/index.ts, packages/deno/src/index.ts, packages/hono/src/index.ts, packages/node/src/index.ts, packages/wasm/src/index.ts, packages/core/src/server.ts, packages/ember/src/index.ts, packages/nitro/src/index.ts, packages/react/src/index.ts, packages/solid/src/index.ts.
What it can do
Capture JavaScript errors and exceptions
JavaScript runtime errors and exceptions → Structured error reports with context data
Generate sourcemap-aware stack traces
Minified JavaScript stack traces and sourcemaps → Human-readable stack traces with original source code references
Track application performance metrics
Application performance data and timing information → Performance monitoring reports and metrics
Monitor browser-based JavaScript applications
Client-side JavaScript application events → Browser error and performance monitoring data
Monitor Node.js server applications
Server-side Node.js application events and errors → Server monitoring data and error reports
Integrate with React applications
React component errors and lifecycle events → React-specific error tracking and component monitoring
Monitor Next.js applications
Next.js application errors and performance data → Full-stack Next.js monitoring reports
Track edge runtime JavaScript execution
Edge runtime JavaScript errors and events → Edge computing monitoring data
Tags
Tech Stack
Media
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.