@sentry/core
Advanced tools
Changelog
8.3.0
This release improves data quality of spans emitted by Express, Fastify, Connect, Koa, Nest.js and Hapi.
feat(node): Ensure connect spans have better data (#12130)
feat(node): Ensure express spans have better data (#12107)
feat(node): Ensure fastify spans have better data (#12106)
feat(node): Ensure hapi spans have better data (#12140)
feat(node): Ensure koa spans have better data (#12108)
feat(node): Ensure Nest.js spans have better data (#12139)
feat(deps): Bump @opentelemetry/instrumentation-express from 0.38.0 to 0.39.0 (#12079)
feat(node): No-code init via --import=@sentry/node/init
(#11999)
When using Sentry in ESM mode, you can now use Sentry without manually calling init like this:
SENTRY_DSN=https://examplePublicKey@o0.ingest.sentry.io/0 node --import=@sentry/node/init app.mjs
When using CommonJS, you can do:
SENTRY_DSN=https://examplePublicKey@o0.ingest.sentry.io/0 node --require=@sentry/node/init app.js
browserProfilingIntegration
is published to CDN (#12158)node:
prefix for node built-ins (#11895)setTimeout
to avoid e.g. angular change detection (#11924)undefined
values in props (#12131)@prisma/instrumentation
from 5.13.0 to 5.14.0 (#12081)Work in this release contributed by @pboling. Thank you for your contribution!
Changelog
8.2.0
beforeSendSpan
hook (#11886)Scope
(#12067)hasTracingEnabled()
if possible (#12066)Changelog
8.1.0
This release mainly fixes a couple of bugs from the initial 8.0.0 release. In addition to the changes below, we updated some initially missed points in our migration guides and documentation.
lastEventId
on isolation scope (#11951) (#12022)awslambda-auto
parseSampleRate
utility function (#12024)eventId
optional and use lastEventId
in report dialog (#12029)Changelog
8.0.0-rc.3
The Bun SDK will now capture global unhandled errors.
http.client
spans if there is an active parent span (#11974)execArgv
are not sent to worker threads (#11963)Changelog
Changes since 8.0.0-rc.3
feat(nextjs): Remove transpileClientSDK
(#11978)
As we are dropping support for Internet Explorer 11 and other other older browser versions wih version 8.0.0
, we are
also removing the transpileClientSDK
option from the Next.js SDK. If you need to support these browser versions,
please configure Webpack and Next.js to down-compile the SDK.
feat(serverless): Do not include performance integrations by default (#11998)
To keep Lambda bundle size reasonable, the SDK no longer ships with all performance (database) integrations by
default. Add the Sentry integrations of the databases and other tools you're using manually to your Sentry.init
call
by following
this guide.
Note that this change does not apply if you use the SDK with the Sentry AWS Lambda layer.
feat(feedback): Simplify public css configuration for feedback (#11985)
fix(feedback): Check for empty user (#11993)
fix(replay): Fix type for replayCanvasIntegration
(#11995)
fix(replay): Fix user activity not being updated in start()
(#12001)
Changelog
8.0.0-rc.2
This release includes adds support for ESM when Sentry.init()
is called within a module imported via the --import
Node.js flag:
node --import ./your-file-with-sentry-init.mjs your-app.mjs
Note that the SDK only supports ESM for node versions 18.19.0
and above, and 20.6.0
above.
@opentelemetry/core
to 1.24.1
and @opentelemetry/instrumentation
to 0.51.1
(#11941)