chore(deps): Bump @sentry/node from 6.18.1 to 7.54.0

Bumps @sentry/node from 6.18.1 to 7.54.0.

Release notes

Sourced from @sentry/node's releases.

7.54.0

Important Changes
feat(core): Add default entries to ignoreTransactions for Healthchecks #8191

All SDKs now filter out health check transactions by default. These are transactions where the transaction name matches typical API health check calls, such as /^.*healthy.*$/ or /^. *heartbeat.*$/. Take a look at this list to learn which regexes we currently use to match transaction names. We believe that these transactions do not provide value in most cases and we want to save you some of your quota by filtering them out by default. These filters are implemented as default values for the top level ignoreTransactions option.

You can disable this filtering by manually specifiying the InboundFilters integration and setting the disableTransactionDefaults option:
Sentry.init({
  //...
  integrations: [new InboundFilters({ disableTransactionDefaults: true })],
})
feat(replay): Add mutationBreadcrumbLimit and mutationLimit to Replay Options (#8228)

The previously experimental options mutationBreadcumbLimit and mutationLimit have been promoted to regular Replay integration options.

A high number of DOM mutations (in a single event loop) can cause performance regressions in end-users' browsers. Use mutationBreadcrumbLimit to send a breadcrumb along with your recording if the mutation limit was reached. Use mutationLimit to stop recording if the mutation limit was reached.
feat(sveltekit): Add source maps support for Vercel (lambda) (#8256)

feat(sveltekit): Auto-detect SvelteKit adapters (#8193)

The SvelteKit SDK can now be used if you deploy your SvelteKit app to Vercel. By default, the SDK's Vite plugin will detect the used adapter and adjust the source map uploading config as necessary. If you want to override the default adapter detection, you can specify the adapter option in the sentrySvelteKit options:
// vite.config.js
export default defineConfig({
  plugins: [
    sentrySvelteKit({
      adapter: 'vercel',
    }),
    sveltekit(),
  ],
});
Currently, the Vite plugin will configure itself correctly for @sveltejs/adapter-auto, @sveltejs/adapter-vercel and @sveltejs/adapter-node.

Important: The SvelteKit SDK is not yet compatible with Vercel's edge runtime. It will only work for lambda functions.

... (truncated)

Changelog

Sourced from @sentry/node's changelog.

7.54.0

Important Changes
feat(core): Add default entries to ignoreTransactions for Healthchecks #8191

All SDKs now filter out health check transactions by default. These are transactions where the transaction name matches typical API health check calls, such as /^.*healthy.*$/ or /^. *heartbeat.*$/. Take a look at this list to learn which regexes we currently use to match transaction names. We believe that these transactions do not provide value in most cases and we want to save you some of your quota by filtering them out by default. These filters are implemented as default values for the top level ignoreTransactions option.

You can disable this filtering by manually specifiying the InboundFilters integration and setting the disableTransactionDefaults option:
Sentry.init({
  //...
  integrations: [new InboundFilters({ disableTransactionDefaults: true })],
})
feat(replay): Add mutationBreadcrumbLimit and mutationLimit to Replay Options (#8228)

The previously experimental options mutationBreadcumbLimit and mutationLimit have been promoted to regular Replay integration options.

A high number of DOM mutations (in a single event loop) can cause performance regressions in end-users' browsers. Use mutationBreadcrumbLimit to send a breadcrumb along with your recording if the mutation limit was reached. Use mutationLimit to stop recording if the mutation limit was reached.
feat(sveltekit): Add source maps support for Vercel (lambda) (#8256)

feat(sveltekit): Auto-detect SvelteKit adapters (#8193)

The SvelteKit SDK can now be used if you deploy your SvelteKit app to Vercel. By default, the SDK's Vite plugin will detect the used adapter and adjust the source map uploading config as necessary. If you want to override the default adapter detection, you can specify the adapter option in the sentrySvelteKit options:
// vite.config.js
export default defineConfig({
  plugins: [
    sentrySvelteKit({
      adapter: 'vercel',
    }),
    sveltekit(),
  ],
});
Currently, the Vite plugin will configure itself correctly for @sveltejs/adapter-auto, @sveltejs/adapter-vercel and @sveltejs/adapter-node.

Important: The SvelteKit SDK is not yet compatible with Vercel's edge runtime. It will only work for lambda functions.

... (truncated)

Commits

d375517 release: 7.54.0
77d4204 Merge pull request #8271 from getsentry/prepare-release/7.54.0
95f8756 meta: Update changelog for 7.54.0
8c6ad15 fix(remix): Don't log missing parameters warning on server-side. (#8269)
c368bc8 fix(remix): Pass loadContext through wrapped document request function (#8268)
6208e57 feat(core): Add default ignoreTransactions for Healthchecks (#8191)
05cf332 feat(sveltekit): Add source maps support for Vercel (lambda) (#8256)
d5551aa ref(replay): Capture parametrized route (#8095)
df5c84a feat(replay): Promote mutationBreadcrumbLimit and mutationLimit to regula...
78454aa fix(wasm): Avoid throwing an error when WASM modules are loaded from blobs (#...
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)

fossasia / open-event-next

chore(deps): Bump @sentry/node from 6.18.1 to 7.54.0 #782

7.54.0

Important Changes

7.54.0

Important Changes