@sentry/node-experimental
Advanced tools
The old version of Sentry SDK for Node.js, without OpenTelemetry support.
Since v8, this is the legacy SDK, and it will most likely be completely removed before v8 is fully stable. It only
exists so that Meta-SDKs like @sentry/nextjs or @sentry/sveltekit can be migrated to the new @sentry/node
step-by-step.
You should instead use @sentry/node.
To use this SDK, call init(options) as early as possible in the main entry module. This will initialize the SDK and
hook into the environment. Note that you can turn off almost all side effects using the respective options. Minimum
supported Node version is Node 14.
// CJS syntax
const Sentry = require('@sentry/node-experimental');
// ESM syntax
import * as Sentry from '@sentry/node-experimental';
Sentry.init({
dsn: '__DSN__',
// ...
});
To set context information or send manual events, use the exported functions of @sentry/node-experimental. Note that
these functions will not perform any action before you have called init():
// 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: [
// ...
],
});
8.0.0-alpha.7
This is the seventh alpha release of Sentry JavaScript SDK v8, which includes a variety of breaking changes.
Read the in-depth migration guide to find out how to address any breaking changes in your code.
We now use OpenTelemetry under the hood to power performance monitoring and tracing in the Next.js SDK.
In v8, you cannot initialize the SDK anymore via Gatsby plugin options. Instead, you have to configure the SDK in a
sentry.config.js file.
We also removed the automatic initialization of browserTracingIntegration. You now have to add this integration
yourself.
scope.setSpan() and scope.getSpan() methods (#11051)runtime and vercel tags (#11291)prismaIntegration by default (#11265)tracePropagationTargets are respected (#11285)SentrySpanProcessor (#11273)instrumentation.ts) (#11266)suppressTracing to avoid capturing otel spans (#11288)startSpan callback throws (#11170)FAQs
Experimental version of a Node SDK using OpenTelemetry for performance instrumentation
The npm package @sentry/node-experimental receives a total of 28 weekly downloads. As such, @sentry/node-experimental popularity was classified as not popular.
We found that @sentry/node-experimental 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
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.