deps: bump @sentry/node from 7.47.0 to 7.48.0

[dependabot]

Bumps @sentry/node from 7.47.0 to 7.48.0.

Release notes

Sourced from @​sentry/node's releases.

7.48.0

Important Changes

• feat(node): Add AsyncLocalStorage implementation of AsyncContextStrategy (#7800)
  • feat(core): Extend AsyncContextStrategy to allow reuse of existing context (#7778)
  • feat(core): Make runWithAsyncContext public API (#7817)
  • feat(core): Add async context abstraction (#7753)
  • feat(node): Adds domain implementation of AsyncContextStrategy (#7767)
  • feat(node): Auto-select best AsyncContextStrategy for Node.js version (#7804)
  • feat(node): Migrate to domains used through 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 Node domain standard library, since AsyncLocalStorage is not supported there. Preliminary testing showed a 30% improvement in latency and rps when making the switch from domains to AsyncLocalStorage on Node 16.

If you want to manually add async context isolation to your application, you can use the new runWithAsyncContext API.

import * as Sentry from '@sentry/node';
const requestHandler = (ctx, next) => {
return new Promise((resolve) => {
Sentry.runWithAsyncContext(async () => {
const hub = Sentry.getCurrentHub();
  hub.configureScope(scope =>
    scope.addEventProcessor(event =>
      Sentry.addRequestDataToEvent(event, ctx.request, {
        include: {
          user: false,
        },
      })
    )
  );
await next();
resolve();
});

});
};

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.

• feat(sveltekit): Remove withSentryViteConfig (#7789)
  • feat(sveltekit): Remove SDK initialization via dedicated files (#7791)

This release removes our withSentryViteConfig wrapper we previously instructed you to add to your vite.config.js file. It is replaced Vite plugins which you simply add to your Vite config, just like the sveltekit() 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:

</tr></table> 

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

7.48.0

Important Changes

• feat(node): Add AsyncLocalStorage implementation of AsyncContextStrategy (#7800)
  • feat(core): Extend AsyncContextStrategy to allow reuse of existing context (#7778)
  • feat(core): Make runWithAsyncContext public API (#7817)
  • feat(core): Add async context abstraction (#7753)
  • feat(node): Adds domain implementation of AsyncContextStrategy (#7767)
  • feat(node): Auto-select best AsyncContextStrategy for Node.js version (#7804)
  • feat(node): Migrate to domains used through 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 Node domain standard library, since AsyncLocalStorage is not supported there. Preliminary testing showed a 30% improvement in latency and rps when making the switch from domains to AsyncLocalStorage on Node 16.

If you want to manually add async context isolation to your application, you can use the new runWithAsyncContext API.

import * as Sentry from '@sentry/node';
const requestHandler = (ctx, next) => {
return new Promise((resolve) => {
Sentry.runWithAsyncContext(async () => {
const hub = Sentry.getCurrentHub();
  hub.configureScope(scope =>
    scope.addEventProcessor(event =>
      Sentry.addRequestDataToEvent(event, ctx.request, {
        include: {
          user: false,
        },
      })
    )
  );
await next();
resolve();
});

});
};

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.

• feat(sveltekit): Remove withSentryViteConfig (#7789)
  • feat(sveltekit): Remove SDK initialization via dedicated files (#7791)

This release removes our withSentryViteConfig wrapper we previously instructed you to add to your vite.config.js file. It is replaced Vite plugins which you simply add to your Vite config, just like the sveltekit() 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:

... (truncated)

Commits

• 253e16d release: 7.48.0
• 452cef5 Merge pull request #7856 from getsentry/prepare-release/7.48.0
• 2a20039 meta(changelog): Update changelog for 7.48.0
• eed0dc9 ref(core): Don't pass hub to runWithAsyncContext callback (#7850)
• 970e108 feat(core): Cache processed stacks for debug IDs (#7825)
• 753a197 chore(repo): Clean up bug report template (#7855)
• 11c68d9 ref(node): Remove unnecessary emitters option from async context abstraction ...
• 3b3c5bd meta: Update changelog to incorporate #7849 and #7850 (#7851)
• d54ff78 feat(replay): Capture request & response headers (#7816)
• dd28a21 Merge pull request #7848 from getsentry/master
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)