@sentry-internal/replay
Advanced tools
Changelog
8.2.1
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
The Sentry JS SDK team is proud to announce the release of version 8.0.0
of Sentry's JavaScript SDKs - it's been a
long time coming! Thanks to everyone for your patience and a special shout out to the brave souls testing preview builds
and reporting issues - we appreciate your support!
We recommend reading the migration guide docs to find out how to address any breaking changes in your code for your specific platform or framework.
To automate upgrading to v8 as much as possible, use our migration codemod @sentry/migr8
:
npx @sentry/migr8@latest
All deprecations from the v7 cycle, with the exception of getCurrentHub()
, have been removed and can no longer be used
in v8. If you have an advanced Sentry SDK setup, we additionally recommend reading the
in-depth migration guide in our repo which highlights all changes with additional details and
information.
The rest of this changelog highlights the most important (breaking) changes and links to more detailed information.
With v8, we dropped support for several old runtimes and browsers
Node SDKs: The Sentry JavaScript SDK v8 now supports Node.js 14.8.0 or higher. This applies to @sentry/node
and all of our node-based server-side sdks (@sentry/nextjs
, @sentry/remix
, etc.). Furthermore, version 8 now ships
with full support for ESM-based node apps using Node.js 18.19.0 or higher.
Browser SDKs: The browser SDKs now require ES2018+ compatible browsers. New minimum browser versions:
For more details, please see the version support section in our migration guide.
In v8, we support a lot more node-based packages than before. In order to ensure auto-instrumentation works, the SDK now needs to be imported and initialized before any other import in your code.
We recommend creating a new file (e.g. instrumentation.js
) to import and initialize the SDK. Then, import the file on
top of your entry file or detailed instructions, check our updated SDK setup docs
initializing the SDK in v8.
The API around performance monitoring and tracing has been streamlined, and we've added support for more integrations out of the box.
Integrations are now simple functions instead of classes. Class-based integrations have been removed:
// old (v7)
Sentry.init({
integrations: [new Sentry.BrowserTracing()],
});
// new (v8)
Sentry.init({
integrations: [Sentry.browserTracingIntegration()],
});
The following packages have been removed or replaced and will no longer be published:
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)Changelog
8.0.0-rc.1
This release contains no changes and was done for technical purposes. This version is considered stable.
For the sake of completeness this changelog entry includes the changes from the previous release candidate:
We recommend to read the detailed migration guide in the docs.
We now support hapi v21 and added tests for it.
When running Sentry in ESM mode, we will now warn you that this is not supported as of now. We are working on ensuring support with ESM builds.
Changelog
8.0.0-rc.0
This is the first release candidate of Sentry JavaScript SDK v8.
We recommend to read the detailed migration guide in the docs.
We now support hapi v21 and added tests for it.
When running Sentry in ESM mode, we will now warn you that this is not supported as of now. We are working on ensuring support with ESM builds.
Changelog
8.0.0-beta.6
This beta release contains various bugfixes and improvements for the v8 beta cycle.
tunnel
support to multiplexed transport (#11806)spanToBaggageHeader
utility (#11881)http.client
spans (#11879)captureFeedback
method (#11428)ioredis
(#11856)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)