[Snyk] Upgrade @sentry/react from 7.16.0 to 8.35.0 #983
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.
Snyk has created this PR to upgrade @sentry/react from 7.16.0 to 8.35.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 217 versions ahead of your current version.
The recommended version was released on 21 days ago.
Release notes
Package name: @sentry/react
Beta release of the official Nuxt Sentry SDK
This release marks the beta release of the
@ sentry/nuxt
Sentry SDK. For details on how to use it, check out theSentry Nuxt SDK README. Please reach out on
GitHub if you have any feedback or concerns.
import()
(#13945)It is no longer required to add a Node
--import
flag. Please update your start command to avoid initializing Sentrytwice (BREAKING CHANGE). The SDK will now apply modifications during the build of your application to allow for
patching of libraries during runtime. If run into issues with this change, you can disable this behavior in your
nuxt.config.ts
and use the--import
flag instead:We now require you to explicitly enable sourcemaps for the clientside so that Sentry can un-minify your errors. We made
this change so source maps aren't accidentally leaked to the public. Enable source maps on the client as follows:
responseHook
withwaitUntil
(#13986)Important Changes
Support for Pinia is added in this release for
@ sentry/vue
. To capture Pinia state data,add
createSentryPiniaPlugin()
to your Pinia store:import { createSentryPiniaPlugin } from '@ sentry/vue';
const pinia = createPinia();
pinia.use(createSentryPiniaPlugin());
This change introduces a new
SentryHttpInstrumentation
to handle non-span related HTTP instrumentation, allowing it torun side-by-side with OTel's
HttpInstrumentation
. This improves support for custom OTel setups and avoids conflictswith Sentry's instrumentation. Additionally, the
spans: false
option is reintroduced forhttpIntegration
to disablespan emission while still allowing custom
HttpInstrumentation
instances (httpIntegration({ spans: false })
).This change adds a new option
trackFetchStreamPerformance
to the browser tracing integration. Only when set totrue
,Sentry will instrument streams via fetch.
Other Changes
suppressTracing
API (#13875)@ opentelemetry/instrumentation-express
to0.43.0
(#13948)@ opentelemetry/instrumentation-fastify
to0.40.0
(#13983)init
is correct in meta frameworks (#13938).set
thesentry-trace
header instead of.append
ing in fetch instrumentation (#13907)ignoreOutgoingRequests
ofhttpIntegration
applies to breadcrumbs (#13970)Work in this release was contributed by @ ZakrepaShe and @ zhiyan114. Thank you for your contributions!
Bundle size 📦
Important Changes
(#13951)
This change adds a new option
trackFetchStreamPerformance
to the browser tracing integration. Only when set totrue
,Sentry will instrument streams via fetch.
Work in this release was contributed by @ ZakrepaShe and @ zhiyan114. Thank you for your contributions!
Other Changes
@ opentelemetry/instrumentation-express
to0.43.0
(#13948)
suppressTracing
API (#13875)(#13763)
import()
(#13945)
(#13965)
init
is correct in meta frameworks(#13938)
(#13962)
(#13953)
sentryOnLoad
(#13952)
(#13961)
Bundle size 📦
replay duration window
Bundle size 📦
Important Changes
Relevant for users of the
@ sentry/nextjs
package: If you have previously configured aSENTRY_IGNORE_API_RESOLUTION_ERROR
environment variable, it is now safe to unset it.Other Changes
getReplay
in replay CDN bundles(#13881)
(#13914)
globalThis
(#13788)
requestAsyncStorageShim.js
template file(#13928)
(#13920)
_not-found
spans for all HTTP methods(#13906)
(#13929)
(#13769)
dataloader
instrumentation from default integrations(#13873)
(#13909)
replay_id
is removed from frozen DSC when stopped(#13893)
sendBufferedReplayOrFlush
to prevent cycles(#13900)
(#13231)
wrapServerRouteWithSentry
to respect ParamMatchers(#13390)
(#13787) (#13854)
(#13905)
vercelWaitUntil
to utils (#13891)Work in this release was contributed by @ trzeciak, @ gurpreetatwal, @ ykzts and @ lizhiyao. Thank you for your
contributions!
Bundle size 📦
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: