@sentry/core

What is @sentry/core?

The @sentry/core package is part of the Sentry SDK for JavaScript, which is designed for real-time monitoring and tracking of application health, errors, and performance issues. It provides the core functionalities needed for initializing and configuring Sentry in your application, handling exceptions, and capturing messages and events.

What are @sentry/core's main functionalities?

Initialization and Configuration

This feature allows you to initialize Sentry in your application with your project's DSN (Data Source Name). It is the first step in integrating Sentry into your project for error tracking and performance monitoring.

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

Capturing Exceptions

This feature enables you to capture exceptions in your code and send them to Sentry for monitoring and analysis. It helps in identifying and debugging errors in your application.

try { myFunction(); } catch (e) { Sentry.captureException(e); }

Capturing Messages

This feature allows you to capture custom messages or log messages in Sentry. It can be used for tracking custom events or information that is not necessarily an error.

Sentry.captureMessage('Something went wrong');

Other packages similar to @sentry/core

logrocket

LogRocket is a frontend application monitoring and product analytics tool that provides session replay, performance monitoring, and error tracking. It offers a more visual approach to debugging by allowing you to replay problems as if you were in your user's shoes. Compared to @sentry/core, LogRocket focuses more on the user experience aspect alongside error tracking.

bugsnag

Bugsnag provides error monitoring and application stability management. It offers features for capturing and tracking errors, diagnosing issues, and improving app stability. Bugsnag is similar to @sentry/core in its core functionalities of error tracking and reporting but also emphasizes application stability metrics and trends.

README

Sentry JavaScript SDK Core

Links

• Official SDK Docs

General

This package contains interface definitions, base classes and utilities for building Sentry JavaScript SDKs, like @sentry/node or @sentry/browser.

Please consider all classes and exported functions and interfaces internal.

Changelog

9.36.0

Important Changes

• feat(node-core): Add node-core SDK (#16745)

This release adds a new SDK @sentry/node-core which ships without any OpenTelemetry instrumententation out of the box. All OpenTelemetry dependencies are peer dependencies and OpenTelemetry has to be set up manually.

Use @sentry/node-core when:

• You already have OpenTelemetry set up
• You need custom OpenTelemetry configuration
• You want minimal dependencies
• You need fine-grained control over instrumentation

Use @sentry/node when:

• You want an automatic setup
• You're new to OpenTelemetry
• You want sensible defaults
• You prefer convenience over control

• feat(node): Deprecate ANR integration (#16832)

The ANR integration has been deprecated and will be removed in future versions. Use eventLoopBlockIntegration from @sentry/node-native instead.

• feat(replay): Add _experiments.ignoreMutations option (#16816)

This replay option allows to configure a selector list of elements to not capture mutations for.

Sentry.replayIntegration({
  _experiments: {
    ignoreMutations: ['.dragging'],
  },
});

Other changes

• feat(deps): bump @prisma/instrumentation from 6.10.1 to 6.11.1 (#16833)
• feat(nextjs): Add flag for suppressing router transition warning (#16823)
• feat(nextjs): Automatically skip middleware requests for tunnel route (#16812)
• feat(replay): Export compression worker from @sentry/replay-internal (#16794)
• fix(browser): Avoid 4xx response for succesful diagnoseSdkConnectivity request (#16840)
• fix(browser): Guard against undefined nextHopProtocol (#16806)
• fix(cloudflare): calculate retries not attempts (#16834)
• fix(nuxt): Parametrize routes on the server-side (#16785)
• fix(vue): Make pageload span handling more reliable (#16799)

Work in this release was contributed by @Spice-King and @stayallive. Thank you for your contributions!