@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
• TypeDoc

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

8.28.0

Important Changes

• Beta release of official NestJS SDK

This release contains the beta version of @sentry/nestjs! For details on how to use it, check out the README. Any feedback/bug reports are greatly appreciated, please reach out on GitHub.

• fix(browser): Remove faulty LCP, FCP and FP normalization logic (#13502)

This release fixes a bug in the @sentry/browser package and all SDKs depending on this package (e.g. @sentry/react or @sentry/nextjs) that caused the SDK to send incorrect web vital values for the LCP, FCP and FP vitals. The SDK previously incorrectly processed the original values as they were reported from the browser. When updating your SDK to this version, you might experience an increase in LCP, FCP and FP values, which potentially leads to a decrease in your performance score in the Web Vitals Insights module in Sentry. This is because the previously reported values were smaller than the actually measured values. We apologize for the inconvenience!

Other Changes

• feat(nestjs): Add SentryGlobalGraphQLFilter (#13545)
• feat(nestjs): Automatic instrumentation of nestjs interceptors after route execution (#13264)
• feat(nextjs): Add bundleSizeOptimizations to build options (#13323)
• feat(nextjs): Stabilize captureRequestError (#13550)
• feat(nuxt): Wrap config in nuxt context (#13457)
• feat(profiling): Expose profiler as top level primitive (#13512)
• feat(replay): Add layout shift to CLS replay data (#13386)
• feat(replay): Upgrade rrweb packages to 2.26.0 (#13483)
• fix(cdn): Do not mangle _metadata (#13426)
• fix(cdn): Fix SDK source for CDN bundles (#13475)
• fix(nestjs): Check arguments before instrumenting with @Injectable (#13544)
• fix(nestjs): Ensure exception and host are correctly passed on when using @WithSentry (#13564)
• fix(node): Suppress tracing for transport request execution rather than transport creation (#13491)
• fix(replay): Consider more things as DOM mutations for dead clicks (#13518)
• fix(vue): Correctly obtain component name (#13484)

Work in this release was contributed by @leopoldkristjansson, @mhuggins and @filips123. Thank you for your contributions!