@sentry/browser

About

Official Sentry SDK for browsers

What detecting @sentry/browser tells you about a site

@sentry/browser means the site ships client-side error and performance monitoring — the team is actively capturing exceptions, breadcrumbs and often session replays in production. Its presence tells you observability is taken seriously and that there's an instrumented release process behind the deploy.

Why the exact @sentry/browser version matters

Sentry's SDK changed its integration API and tree-shaking model significantly across v7 and v8, and the bundled version determines which features (tracing, replay, profiling) are wired in and how much monitoring runtime the page carries. The exact version also reveals how current the observability tooling is.

@sentry/browser in a real-world stack

When you find @sentry/browser in a bundle, it rarely travels alone. Framework-specific wrappers like @sentry/react or @sentry/nextjs, which pull @sentry/browser in transitively.

Quick facts

What @sentry/browser pulls in

@sentry/browser declares 6 direct dependencies — each one also rides into any bundle that ships @sentry/browser, so they are detection targets too. Reading them is a quick way to understand the package's real footprint .

How Sourcemap Explorer detects @sentry/browser

@sentry/browser ships as v10.69.0, published 2026-07-29 and carries 6 direct dependencies, 728 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when @sentry/browser rides inside a deployed bundle — here is how the detection works.

We catch @sentry/browser from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/@sentry/browser/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.

1. 1

   Confirm the site exposes sourcemaps

   In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment — that map is where the `@sentry/browser` paths live.

2. 2

   Find the package in the bundle

   Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/@sentry/browser/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/@sentry/browser/package.json` gives you the exact installed version.

3. 3

   Read the version directly from package.json

   Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/@sentry/browser/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.

Major releases of @sentry/browser

When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the @sentry/browser version a site actually ships against the ecosystem.

Recent security advisories for @sentry/browser

The 1 most recent advisories affecting some versions of @sentry/browser, aggregated from OSV.dev (GitHub Advisory + CVE data). A listing here doesn't mean the version a given site ships is affected — each advisory applies to a specific version range. Sourcemap Explorer reads the exact bundled version so you can check it against these ranges.

1. MODERATEGHSA-593m-55hh-j8gv· 2024-10-03

   Sentry SDK Prototype Pollution gadget in JavaScript SDKs

Recent versions

@sentry/browser README

Live mirror of the GitHub README, for reference. Updated whenever the repo's default branch changes.

Bad software is everywhere, and we're tired of it. Sentry is on a mission to help developers write better software faster, so we can get back to enjoying technology. If you want to join us Check out our open positions

Official Sentry SDKs for JavaScript

This is the next line of Sentry JavaScript SDKs, comprised in the @sentry/ namespace. It will provide a more convenient interface and improved consistency between various JavaScript environments.

Links

• 
• 
• 
• 
• 

Contents

• Contributing
• Supported Platforms
• Installation and Usage
• Other Packages
• Bug Bounty Program

Supported Platforms

For each major JavaScript platform, there is a specific high-level SDK that provides all the tools you need in a single package. Please refer to the README and instructions of those SDKs for more detailed information:

• @sentry/browser: SDK for Browsers
• @sentry/node: SDK for Node including integrations for Express
• @sentry/angular: Browser SDK for Angular
• @sentry/astro: SDK for Astro
• @sentry/ember: Browser SDK for Ember
• @sentry/react: Browser SDK for React
• @sentry/svelte: Browser SDK for Svelte
• @sentry/sveltekit: SDK for SvelteKit
• @sentry/vue: Browser SDK for Vue
• @sentry/solid: Browser SDK for Solid
• @sentry/gatsby: SDK for Gatsby
• @sentry/nestjs: SDK for NestJS
• @sentry/nextjs: SDK for Next.js
• @sentry/nitro: SDK for Nitro
• @sentry/remix: SDK for Remix
• @sentry/tanstackstart-react: SDK for TanStack Start React
• @sentry/aws-serverless: SDK for AWS Lambda Functions
• @sentry/google-cloud-serverless: SDK for Google Cloud Functions
• @sentry/electron: SDK for Electron with support for native crashes
• @sentry/react-native: SDK for React Native with support for native crashes
• @sentry/capacitor: SDK for Capacitor Apps and Ionic with support for native crashes
• @sentry/effect: SDK for Effect (Alpha)
• @sentry/bun: SDK for Bun
• @sentry/elysia: SDK for Elysia
• @sentry/deno: SDK for Deno
• @sentry/cloudflare: SDK for Cloudflare

Version Support Policy

We recognize the importance of continued support for our SDK across different versions. Our commitment is to provide bug fixes and feature updates for older versions based on community demand and usage.

Installation and Usage

To install a SDK, simply add the high-level package, for example:

npm install --save @sentry/browser
yarn add @sentry/browser

Setup and usage of these SDKs always follows the same principle.

import * as Sentry from '@sentry/browser';

Sentry.init({
  dsn: '__DSN__',
  // ...
});

Sentry.captureMessage('Hello, world!');

Other Packages

Besides the high-level SDKs, this repository contains shared packages, helpers and configuration used for SDK development. If you're thinking about contributing to or creating a JavaScript-based SDK, have a look at the resources below:

• @sentry/replay: Provides the integration for Session Replay.
• @sentry/core: The base for all JavaScript SDKs with interfaces, type definitions and base classes.

Bug Bounty Program

Our bug bounty program aims to improve the security of our open source projects by encouraging the community to identify and report potential security vulnerabilities. Your reward will depend on the severity of the identified vulnerability.

Our program is currently running on an invitation basis. If you're interested in participating, please send us an email to security@sentry.io and tell us, that you are interested in auditing this repository.

For more details, please have a look at https://sentry.io/security/#vulnerability-disclosure.

Contributors

Thanks to everyone who contributed to the Sentry JavaScript SDK!

FAQ