@sentry/browser

What is @sentry/browser?

The @sentry/browser package is a JavaScript SDK for Sentry, which is an error tracking service that helps developers monitor and fix crashes in real time. The SDK hooks into the global error handling mechanisms of the browser and captures unhandled exceptions and other errors, providing rich context and insights into the underlying issues.

What are @sentry/browser's main functionalities?

Error Tracking

This feature automatically captures JavaScript exceptions and sends them to Sentry for analysis and tracking. The code initializes Sentry with a DSN (Data Source Name) and sets up a global error handler to capture exceptions.

Sentry.init({ dsn: 'YOUR_DSN' });

window.onerror = function (errorMsg, url, lineNumber, column, errorObj) {
  Sentry.captureException(errorObj);
  return false;
}

Manual Error Reporting

This allows developers to manually report exceptions or errors to Sentry. The code block demonstrates how to catch an error in a try-catch block and manually send it to Sentry using the captureException method.

Sentry.init({ dsn: 'YOUR_DSN' });

try {
  // Code that might fail
} catch (error) {
  Sentry.captureException(error);
}

Performance Monitoring

This feature enables performance monitoring by capturing transactions and spans. The code initializes Sentry with a sample rate for transactions and demonstrates how to start and finish a transaction, which can be used to measure the performance of operations.

Sentry.init({ dsn: 'YOUR_DSN', tracesSampleRate: 1.0 });

const transaction = Sentry.startTransaction({ name: 'test transaction' });
// ... some code ...
transaction.finish();

Breadcrumbs

Breadcrumbs are a trail of events that happened prior to an issue. This feature allows you to record breadcrumbs manually. The code shows how to add a breadcrumb for an authentication event.

Sentry.init({ dsn: 'YOUR_DSN' });

Sentry.addBreadcrumb({
  category: 'auth',
  message: 'User authenticated',
  level: Sentry.Severity.Info
});

User Feedback

This feature allows you to collect user feedback when an error occurs. The code initializes Sentry and then shows a dialog to the user to collect feedback for a specific event.

Sentry.init({ dsn: 'YOUR_DSN' });

Sentry.showReportDialog({ eventId: 'event_id' });

Other packages similar to @sentry/browser

bugsnag-js

Bugsnag provides similar error tracking and monitoring capabilities as Sentry. It offers real-time error reporting and can be used to monitor application stability. Bugsnag also provides features for error diagnostics and supports multiple platforms.

raygun4js

Raygun is another error monitoring service that offers crash reporting with detailed diagnostics. It supports real-time error tracking and performance monitoring, and it can be used to identify and diagnose software errors and performance issues.

rollbar-browser

Rollbar offers real-time error tracking and is similar to Sentry in its capabilities. It includes features like telemetry, person tracking, and version tracking. Rollbar provides a comprehensive dashboard for monitoring and analyzing errors.

README

Official Sentry SDK for Browsers

Links

• Official SDK Docs

Usage

To use this SDK, call Sentry.init(options) as early as possible after loading the page. This will initialize the SDK and hook into the environment. Note that you can turn off almost all side effects using the respective options.

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

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

To set context information or send manual events, use the exported functions of @sentry/browser. Note that these functions will not perform any action before you have called Sentry.init():

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

// Set user information, as well as tags and further extras
Sentry.setExtra('battery', 0.7);
Sentry.setTag('user_mode', 'admin');
Sentry.setUser({ id: '4711' });

// Add a breadcrumb for future events
Sentry.addBreadcrumb({
  message: 'My Breadcrumb',
  // ...
});

// Capture exceptions, messages or manual events
Sentry.captureMessage('Hello, world!');
Sentry.captureException(new Error('Good bye'));
Sentry.captureEvent({
  message: 'Manual',
  stacktrace: [
    // ...
  ],
});

Changelog

9.31.0

Important Changes

• feat(nextjs): Add option for auto-generated random tunnel route (#16626)

Adds an option to automatically generate a random tunnel route for the Next.js SDK. This helps prevent ad blockers and other tools from blocking Sentry requests by using a randomized path instead of the predictable /monitoring endpoint.

• feat(core): Allow to pass scope & client to getTraceData (#16633)

Adds the ability to pass custom scope and client parameters to the getTraceData function, providing more flexibility when generating trace data for distributed tracing.

Other Changes

• feat(core): Add support for x-forwarded-host and x-forwarded-proto headers (#16687)
• deps: Remove unused @sentry/opentelemetry dependency (#16677)
• deps: Update all bundler plugin instances to latest & allow caret ranges (#16641)
• feat(deps): Bump @prisma/instrumentation from 6.8.2 to 6.9.0 (#16608)
• feat(flags): add node support for generic featureFlagsIntegration and move utils to core (#16585)
• feat(flags): capture feature flag evaluations on spans (#16485)
• feat(pino): Add initial package for @sentry/pino-transport (#16652)
• fix: Wait for the correct clientWidth/clientHeight when showing Feedback Screenshot previews (#16648)
• fix(browser): Remove usage of Array.at() method (#16647)
• fix(core): Improve safeJoin usage in console logging integration (#16658)
• fix(google-cloud-serverless): Make CloudEvent type compatible (#16661)
• fix(nextjs): Fix lookup of instrumentation-client.js file (#16637)
• fix(node): Ensure graphql errors result in errored spans (#16678)