@sentry/bun
Advanced tools
The Sentry Bun SDK is in beta. Please help us improve the SDK by reporting any issues or giving us feedback.
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.
// CJS Syntax
const Sentry = require('@sentry/bun');
// ESM Syntax
import * as Sentry from '@sentry/bun';
Sentry.init({
dsn: '__DSN__',
// ...
});
To set context information or send manual events, use the exported functions of @sentry/bun. 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: [
// ...
],
});
10.12.0
ref: Add and Adjust error event mechanism values
This release includes a variety of changes aimed at setting the mechanism field on errors captured automatically by the Sentry SDKs. The intention is to clearly mark which instrumentation captured an error. In addition, some instrumentations previously did not yet annotate the error as handled or unhandled which this series of PRs corrects as well.
Released in 10.12.0:
mechanism on error events captured by astro middleware (#17613)mechanism of errors captured in Bun.serve (#17616)mechanisms and durable object origin (#17618)mechanism in captureConsoleIntegration (#17633)mechanism (#17622)linkedErrors mechanism logic (#17600)mechanism of errors caught by globalHandlersIntegration (#17635)mechanisms (#17543)mechanism to cron instrumentations (#17544)mechanism.type to worker thread errors from childProcessIntegration (#17578)mechanism of onUnhandledRejection and onUnhandledException integrations (#17636)mechanism.type in error events (#17599)reactErrorHandler and adjust mechanism in ErrorBoundary (#17602)captureRemixServerException (#17629)replayIntegration in debug mode (#17606)mechanism to error captured by withSentryErrorBoundary (#17607)mechanism of error events (#17646)Released in 10.11.0:
mechanism.type to errors captured by httpClientIntegration (#17254)mechanism.type in browserApiErrorsIntergation (#17251)mechanism.type to trpcMiddleware errors (#17287)mechanisms and span origins to openAiIntegration (#17288)mechanism to captured errors (#17312)prismaIntegration works with Prisma 5 (#17595)We used to require to pass in the v5 version of @prisma/instrumentation into prismaIntegration({ prismaInstrumentation: new PrismaInstrumentation() }), if you wanted to get full instrumentation for Prisma v5. However, it turns out this does not work on v10 of the SDK anymore, because @prisma/instrumentation@5 requires OTEL v1.
With this release, we dropped the requirement to configure anything to get v5 support of Prisma. You do not need to configure anything in the integration anymore, and can remove the dependency on @prisma/instrumentation@5 if you had it in your application. You only need to configure the tracing preview feature according to our docs.
TracesSamplerSamplingContext type (#17523)prismaIntegration works with Prisma v5 (#17595)parentSpanId stays consistent during trace in TwP mode (#17526)step.do (#17582)_platform properties in Nitro 2.11.7+ (#17596)shimmer (#17597) - ref(nuxt): Add and adjust mechanism.type in error events (#17599)fetchTransport error handling (#17661).claude/settings.local.json to .claude/settings.json (#17591)flushIfServerless test (#17610)FAQs
Official Sentry SDK for bun
The npm package @sentry/bun receives a total of 51,442 weekly downloads. As such, @sentry/bun popularity was classified as popular.
We found that @sentry/bun demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 10 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.
Research
/Security News
Socket identified 80 fake candidates targeting engineering roles, including suspected North Korean operators, exposing the new reality of hiring as a security function.
Application Security
/Research
/Security News
Socket detected multiple compromised CrowdStrike npm packages, continuing the "Shai-Hulud" supply chain attack that has now impacted nearly 500 packages.
Research
/Security News
Malicious update to @ctrl/tinycolor on npm is part of a supply-chain attack hitting 40+ packages across maintainers