Bump @sentry/node from 7.38.0 to 7.51.0

[dependabot]

Bumps @sentry/node from 7.38.0 to 7.51.0.

Release notes

Sourced from @​sentry/node's releases.

7.51.0

Important Changes

• feat(sveltekit): Auto-wrap load functions with proxy module (#7994)

@sentry/sveltekit now auto-wraps load functions in

• +(page|layout).(ts|js) files (universal loads)
• +(page|layout).server.(ts|js) files (server-only loads)

This means that you don't have to manually add the wrapLoadWithSentry and wrapServerLoadWithSentry functions around your load functions. The SDK will not interfere with already wrapped load functions.

For more details, take a look at the Readme

• chore(angular): Upgrade peerDependencies to Angular 16 (#8035)

We now officially support Angular 16 in @sentry/angular-ivy. Note that @sentry/angular does not support Angular 16.

• feat(node): Add ability to send cron monitor check ins (#8039)

Note: This release contains a bug with generating cron monitors. We recommend you wait till the next release of the JS SDK to use cron monitoring functionality

This release adds Sentry cron monitoring support to the Node SDK.

To monitor your cron jobs, send check-ins everytime you execute your cron jobs to Sentry. You can do this with the captureCheckIn method exported from the SDK. First you must send an in_progress, checkin, then you can send one with status ok or error based on what happened with your cron job.

const Sentry = require('@sentry/node');
// ...
Sentry.captureCheckIn({
// make sure this is the same slug as what you set up your
// Sentry cron monitor with.
monitorSlug: 'dailyEmail',
status: 'in_progress',
});
const startTime = timeInSeconds();
runTask();
Sentry.captureCheckIn({
monitorSlug: 'dailyEmail',
status: 'ok',
duration: timeInSeconds() - startTime,
});

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

7.51.0

Important Changes

• feat(sveltekit): Auto-wrap load functions with proxy module (#7994)

@sentry/sveltekit now auto-wraps load functions in

• +(page|layout).(ts|js) files (universal loads)
• +(page|layout).server.(ts|js) files (server-only loads)

This means that you don't have to manually add the wrapLoadWithSentry and wrapServerLoadWithSentry functions around your load functions. The SDK will not interfere with already wrapped load functions.

For more details, take a look at the Readme

• chore(angular): Upgrade peerDependencies to Angular 16 (#8035)

We now officially support Angular 16 in @sentry/angular-ivy. Note that @sentry/angular does not support Angular 16.

• feat(node): Add ability to send cron monitor check ins (#8039)

This release adds Sentry cron monitoring support to the Node SDK.

To monitor your cron jobs, send check-ins everytime you execute your cron jobs to Sentry. You can do this with the captureCheckIn method exported from the SDK. First you must send an in_progress, checkin, then you can send one with status ok or error based on what happened with your cron job.

const Sentry = require('@sentry/node');
// ...
Sentry.captureCheckIn({
// make sure this is the same slug as what you set up your
// Sentry cron monitor with.
monitorSlug: 'dailyEmail',
status: 'in_progress',
});
const startTime = timeInSeconds();
runTask();
Sentry.captureCheckIn({
monitorSlug: 'dailyEmail',
status: 'ok',
duration: timeInSeconds() - startTime,
});

Additional Features and Fixes

... (truncated)

Commits

• 8b4aad8 release: 7.51.0
• e775104 Merge pull request #8042 from getsentry/prepare-release/7.51.0
• ba9e198 meta(changelog): Update CHANGELOG for 7.51.0
• 9ea2bca feat(node): Add ability to send cron monitor check ins (#8039)
• 43d9fa9 feat(sveltekit): Auto-wrap load functions with proxy module (#7994)
• 2395107 chore(angular): Clarify @sentry/angular and @sentry/angular-ivy version c...
• 44eee4c chore(angular): Upgrade peerDependencies to Angular 16 (#8035)
• 4800458 test: Refactor playwright bundle generation (#8029)
• b9fb55f fix(remix): Export Integration type declaration as union type (#8016)
• 184622d fix(integrations): Handle windows paths with no prefix or backslash prefix in...
• 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)

[dependabot]

Superseded by #323.