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.
Sentry JavaScript SDK Core
Links
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
.
8.34.0
Important Changes
- ref(nextjs): Remove dead code (#13828)
Relevant for users of the @sentry/nextjs
package: If you have previously configured a
SENTRY_IGNORE_API_RESOLUTION_ERROR
environment variable, it is now safe to unset it.
Other Changes
- feat(cdn): Export
getReplay
in replay CDN bundles
(#13881) - feat(replay): Clear fallback buffer when switching buffers
(#13914)
- feat(replay): Upgrade rrweb packages to 2.28.0 (#13732)
- fix(docs): Correct supported browsers due to
globalThis
(#13788) - fix(nextjs): Adjust path to
requestAsyncStorageShim.js
template file
(#13928) - fix(nextjs): Detect new locations for request async storage to support Next.js v15.0.0-canary.180 and higher
(#13920)
- fix(nextjs): Drop
_not-found
spans for all HTTP methods
(#13906) - fix(nextjs): Fix resolution of request storage shim fallback
(#13929)
- fix(node): Ensure graphql options are correct when preloading
(#13769)
- fix(node): Local variables handle error (#13827)
- fix(node): Remove
dataloader
instrumentation from default integrations
(#13873) - fix(nuxt): Create declaration files for Nuxt module
(#13909)
- fix(replay): Ensure
replay_id
is removed from frozen DSC when stopped
(#13893) - fix(replay): Try/catch
sendBufferedReplayOrFlush
to prevent cycles
(#13900) - fix(sveltekit): Ensure trace meta tags are always injected
(#13231)
- fix(sveltekit): Update
wrapServerRouteWithSentry
to respect ParamMatchers
(#13390) - fix(wasm): Integration wasm uncaught WebAssembly.Exception
(#13787) (#13854)
- ref(nextjs): Ignore sentry spans based on query param attribute
(#13905)
- ref(utils): Move
vercelWaitUntil
to utils (#13891)
Work in this release was contributed by @trzeciak, @gurpreetatwal, @ykzts and @lizhiyao. Thank you for your
contributions!