chore(deps): update JavaScript SDK to v8.15.0 #3895
+125
−85
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps scripts/update-javascript.sh from 7.117.0 to 8.15.0.
Auto-generated by a dependency updater.
Changelog
8.15.0
on
(#11710)spanTimeInputToSeconds
for otel span exporter (#12699)lazyLoadIntegration
(#12766)jsxRuntime: 'classic'
to prevent breaking react 17 (#12775)getStack()
(#12737)Work in this release was contributed by arturovt and jaulz. Thank you for your contributions!
8.14.0
Important Changes
The
sentry/nestjs
SDK no longer captures 4xx errors automatically.Other Changes
JSX
(#12691)registerEsmLoaderHooks
option (#12684)afterAllSetup
instead of next tick (#12709)Work in this release was contributed by quisido. Thank you for your contribution!
8.13.0
Important Changes
sentry/nestjs
)in alpha state. The SDK is a drop-in replacement for the Sentry Node SDK (
sentry/node
) supporting the same set offeatures. See the docs for how to use the SDK.
Other Changes
2.20.1
(#12641)8.12.0
Important Changes
This release introduces breaking changes to the
sentry/solid
package (which is currently out in alpha).We've made it easier to get started with the solid router integration by removing the need to pass use* hooks
explicitly to
solidRouterBrowserTracingIntegration
. ImportsolidRouterBrowserTracingIntegration
fromsentry/solid/solidrouter
and add it toSentry.init
Sentry.init()
now returns a client directly, so you don't need to explicitly callgetClient()
anymore:deleteSourcemapsAfterUpload
option (#12457)This adds an easy way to delete sourcemaps immediately after uploading them:
maxSpanWaitDuration
(#12610)Adds configuration option for the max. duration in seconds that the SDK will wait for parent spans to be finished before
discarding a span. The SDK will automatically clean up spans that have no finished parent after this duration. This is
necessary to prevent memory leaks in case of parent spans that are never finished or otherwise dropped/missing. However,
if you have very long-running spans in your application, a shorter duration might cause spans to be discarded too early.
In this case, you can increase this duration to a value that fits your expected data.
Other Changes
window.Sentry
(#12580)isRemixV2
as optional in exposed types. (#12614)Work in this release was contributed by n4bb12. Thank you for your contribution!
8.11.0
Important Changes
parentSpan
option tostartSpan*
APIs (#12567)We've made it easier to create a span as a child of a specific span via the startSpan* APIs. This should allow you to
explicitly manage the parent-child relationship of your spans better.
Other Changes
sentry/node
exports from framework SDKs. (#12589)8.10.0
Important Changes
opentelemetry-instrumentation-remix
. (#12110)You can now simplify your remix instrumentation by opting-in like this:
With this setup, you do not need to add e.g.
wrapExpressCreateRequestHandler
anymore. Additionally, the quality of thecaptured data improves. The old way to use
sentry/remix
continues to work, but it is encouraged to use the new setup.Other Changes
thirdPartyErrorFilterIntegration
fromsentry/browser
(#12512)tags
field to any feedback config param (#12197)getDynamicSamplingContextFromSpan
(#12522)captureRemixServerException
from client SDK (#12497)Work in this release was contributed by AndreyKovanov and kiliman. Thank you for your contributions!
8.9.2
8.9.1
Important changes
feat(solid): Add Solid SDK
This release adds a dedicated SDK for Solid JS in alpha state with instrumentation for
Solid Router and a custom
ErrorBoundary
. See thepackage README for how to use
the SDK.
Other changes
op
to Otel-generated lambda function root span (#12430)awslambda-auto
(#12392)Work in this release was contributed by soch4n. Thank you for your contribution!
8.9.0
This release failed to publish correctly, please use
8.9.1
instead.8.8.0
This upgrades the OpenTelemetry dependencies to the latest versions and makes OTEL use
import-in-the-middle
v1.8.0
.This should fix numerous issues with using OTEL instrumentation with ESM.
High level issues fixed with OTEL + ESM:
tsx
or similar libraries.date-fns
.openai
.ENOENT: no such file or directory
bugs that libraries likediscord.js
surface.
If you are still encountering issues with OpenTelemetry instrumentation and ESM, please let us know.
2.18.0
(#12381)thirdPartyErrorFilterIntegration
(#12267)mget
command in caching functionality (#12380)clientTraceMetadata
option (#12323)sentry
property on Next.js config object (#12366)(#12360)
Work in this release contributed by dohooo, mohd-akram, and ykzts. Thank you for your contributions!
8.7.0
Important Changes
feat(react): Add TanStack Router integration (#12095)
This release adds instrumentation for TanStack router with a new
tanstackRouterBrowserTracingIntegration
in thesentry/react
SDK:Other Changes
sourceMappingURL
comment on client whennextConfig.productionBrowserSourceMaps: true
isset (#12278)
8.6.0
Important Changes
feat(metrics): Add
timings
method to metrics (#12226)This introduces a new method,
metrics.timing()
, which can be used in two ways:second
as unit:create an inactive span around the callback and at the end emit a metric with the duration of the span in seconds:
feat(react): Add
Sentry.reactErrorHandler
(#12147)This PR introduces
Sentry.reactErrorHandler
, which you can use in React 19 as follows:For more details, take a look at the PR. Our
documentation will be updated soon!
Other Changes
8.5.0
Important Changes
This release adds support for React 19 in the
sentry/react
SDK package.sentry/node/preload
hook (#12213)This release adds a new way to initialize
sentry/node
, which allows you to use the SDK with performanceinstrumentation even if you cannot call
Sentry.init()
at the very start of your app.First, run the SDK like this:
Now, you can initialize and import the rest of the SDK later or asynchronously:
For more details, head over to the
PR Description of the new feature. Our docs will be updated
soon with a new guide.
Other Changes
startNewTrace
API (#12138)captureFeedback()
(#12216)SerializedSession
in session envelope items (#11979)waitUntil
to defer freezing of Vercel Lambdas (#12133)Module._resolveFilename
in Lambda layer bundle (#12232)ImportInTheMiddle
(#12233)prisma/instrumentation
to use default import (#12185)inspector
asynchronously (#12231)8.4.0
Important Changes
If you are using Next.js version
14.3.0-canary.64
or above, the Sentry Next.js SDK will now trace clientside pageloadswith React Server Components. This means, that client-side errors like
Error: An error occurred in the Server Components render.
, which previously didn't give you much information on howthat error was caused, can now be traced back to a specific error in a server component.
This release guarantees support for Angular 18 with
sentry/angular
.Other Changes
8.3.0
Important Changes
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:
When using CommonJS, you can do:
Other Changes
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!
8.2.1
8.2.0
beforeSendSpan
hook (#11886)Scope
(#12067)hasTracingEnabled()
if possible (#12066)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 uselastEventId
in report dialog (#12029)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 along 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!
How to Upgrade to Version 8:
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
:All deprecations from the v7 cycle, with the exception of
getCurrentHub()
, have been removed and can no longer be usedin 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.
Version Support
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 shipswith 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.
Initializing Server-side SDKs (Node, Bun, Deno, Serverless):
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 ontop of your entry file or detailed instructions, check our updated SDK setup docs
initializing the SDK in v8.
Performance Monitoring Changes
The API around performance monitoring and tracing has been streamlined, and we've added support for more integrations
out of the box.
Functional Integrations
Integrations are now simple functions instead of classes. Class-based integrations
have been removed:
Package removal
The following packages have been removed or replaced and will no longer be published:
sentry/hub
sentry/tracing
sentry/integrations
sentry/serverless
sentry/replay
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 arealso 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
callby 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)8.0.0-rc.3
Important Changes
The Bun SDK will now capture global unhandled errors.
Other Changes
http.client
spans if there is an active parent span (#11974)execArgv
are not sent to worker threads (#11963)8.0.0-rc.2
Important Changes
This release includes adds support for ESM when
Sentry.init()
is called within a module imported via the--import
Node.js flag:
Note that the SDK only supports ESM for node versions
18.19.0
and above, and20.6.0
above.Other Changes
opentelemetry/core
to1.24.1
andopentelemetry/instrumentation
to0.51.1
(#11941)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.
Important Changes
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.
Other Changes
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.
Important Changes
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.
Other Changes
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)8.0.0-beta.5
This beta release contains various bugfixes and improvements for the v8 beta cycle.
Important Changes
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.
Other Changes
transactionName
to isolation scope for requests (#11786)startInactiveSpan
(#11788)trace
envelope header to span envelope (#11699)start*Span
APIs (#11696)withMonitor
callback inwithIsolationScope
(#11797)transactionName
to isolation scope for Next.js server side features (#11782)opentelemetry/instrumentation
(#11810)wrapHandleErrorWithSentry
(#10370)formData
asaction
span data. (#10836)transactionName
for Remix server features (#11784)showReportDialog
in root context (#11703)loader
,action
anddocumentRequest
errors (#11793)captureException()
,captureMessage()
, andcaptureEvent()
(#11805)requestDataIntegration
(#11513)onlyIfParent
for recording component update spans (#11809)8.0.0-beta.4
Important Changes
INP web vital support was now forward-ported to version 8. Recording of INP data is enabled by default.
The default limit of queued events to be sent was increased from 30 to 64 events. You may observe a higher memory
footprint of the SDK. You can override this limit by setting the
transportOptions.bufferSize
option inSentry.init()
.A
maxCanvasSize
option was added to thereplayCanvasIntegration
to disallow capturing of canvases larger than acertain size. This value defaults to
1280
which will not capture canvases bigger than 1280x1280 pixels.Other Changes
opentelemetry/instrumentation-http
to0.48.0
(#11745)opentelemetry/api
dependency from Next.js package (#11717)