fix(deps): update dependency @sentry/browser to ^7.48.0 #555
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.
This PR contains the following updates:
^7.47.0
->^7.48.0
Release Notes
getsentry/sentry-javascript
v7.48.0
Compare Source
Important Changes
AsyncLocalStorage
implementation ofAsyncContextStrategy
(#7800)AsyncContextStrategy
to allow reuse of existing context (#7778)runWithAsyncContext
public API (#7817)domain
implementation ofAsyncContextStrategy
(#7767)AsyncContextStrategy
for Node.js version (#7804)AsyncContextStrategy
(#7779)This release switches the SDK to use
AsyncLocalStorage
as the async context isolation mechanism in the SDK for Node 14+. For Node 10 - 13, we continue to use the Nodedomain
standard library, sinceAsyncLocalStorage
is not supported there. Preliminary testing showed a 30% improvement in latency and rps when making the switch from domains toAsyncLocalStorage
on Node 16.If you want to manually add async context isolation to your application, you can use the new
runWithAsyncContext
API.If you're manually using domains to isolate Sentry data, we strongly recommend switching to this API!
In addition to exporting
runWithAsyncContext
publicly, the SDK also uses it internally where we previously used domains.withSentryViteConfig
(#7789)This release removes our
withSentryViteConfig
wrapper we previously instructed you to add to yourvite.config.js
file. It is replaced Vite plugins which you simply add to your Vite config, just like thesveltekit()
Vite plugins. We believe this is a more transparent and Vite/SvelteKit-native way of applying build time modifications. Here's how to use the plugins:Take a look at the
README
for updated instructions!Furthermore, with this transition, we removed the possibility to intialize the SDK in dedicated
sentry.(client|server).config.js
files. Please use SvelteKit's hooks files to initialize the SDK.Please note that these are breaking changes! We're sorry for the inconvenience but the SvelteKit SDK is still in alpha stage and we want to establish a clean and SvelteKit-friendly API before making the SDK stable. You have been warned ;)
This release adds automatic upload of source maps to the SvelteKit SDK. No need to configure anything other than adding our Vite plugins to your SDK. The example above shows you how to do this.
Please make sure to follow the
README
to specify your Sentry auth token, as well as org and project slugs.- feat(replay): Capture request & response headers (#7816)
Replay now captures the
content-length
,content-type
, andaccept
headers from requests and responses automatically.Additional Features and Fixes
getReplayId()
method (#7822)BrowserTransportOptions
to support offline transport options (#7775)applyDebugMetadata
for error events (#7824)reuseExisting
does not need to call bind on domain (#7780)trpcMiddleware
factory synchronous (#7802)Configuration
📅 Schedule: Branch creation - "before 5am on monday" in timezone Europe/Vienna, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.