@sentry/core
Advanced tools
Package description
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.
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');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 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.
Changelog
8.0.0-beta.5
This beta release contains various bugfixes and improvements for the v8 beta cycle.
We now officially support Svelte 5.
Starting with this version, spans for outgoing fetch/xhr requests will be captured even if no pageload/navigation span is ongoing. This means that you will be able to have a more complete trace, especially for web applications that make a lot of HTTP requests on longer lived pages.
transactionName to isolation scope for requests (#11786)startInactiveSpan (#11788)trace envelope header to span envelope (#11699)start*Span APIs (#11696)withMonitor callback in withIsolationScope (#11797)transactionName to isolation scope for Next.js server side features (#11782)@opentelemetry/instrumentation (#11810)wrapHandleErrorWithSentry (#10370)formData as action span data. (#10836)transactionName for Remix server features (#11784)showReportDialog in root context (#11703)loader, action and documentRequest errors (#11793)captureException(), captureMessage(), and
captureEvent() (#11805)requestDataIntegration (#11513)onlyIfParent for recording component update spans (#11809)Readme
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.
FAQs
Base implementation for all Sentry JavaScript SDKs
We found that @sentry/core demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 11 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Ecma TC39 is meeting this week and has moved key ECMAScript proposals forward, advancing Deferred Import Evaluation, Error.isError(), RegExp Escaping, and Promise.try to the next stages.
Security News
Researchers have demonstrated that teams of LLM agents can exploit zero-day vulnerabilities with a 53% success rate, and the costs of using AI to do so are rapidly becoming more affordable than hiring a human penetration tester.
Security News
In an unprecedented surge, May 2024 saw the publication of over 5,000 CVEs, marking a historic milestone in cybersecurity with an average of 164 CVEs per day, nearly double the 2023 daily average.