Deprecate Nest usage in @sentry/node
#14242
Comments
lforst
changed the title
@sentry/node@sentry/node
lforst
changed the title
@sentry/node@sentry/node
3 tasks
lforst
added a commit
that referenced
this issue
Nov 15, 2024
Ref #14242 The NestJS SDK is stable enough for us to remove this label. All the breaking changes we do to the SDK are gonna end up in v9.
This was referenced Nov 19, 2024
A PR closing this issue has just been released 🚀This issue was referenced by PR #14374, which was included in the 8.40.0 release. |
onurtemizkan
pushed a commit
that referenced
this issue
Nov 22, 2024
Ref #14242 The NestJS SDK is stable enough for us to remove this label. All the breaking changes we do to the SDK are gonna end up in v9.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Users should use
@sentry/nestjsinstead of@sentry/nodewith the nest integration.While the nest integration is automatically added, we can add a deprecation warning to
setupNestErrorHandlerwhen used from@sentry/node.In v9, we'll remove the nest integration from
@sentry/node, in favor of users using the nest SDK directly.NOTE: We should only do this once we removed any beta warnings/labels from the Nest SDK.
NOTE by @lforst: This should likely also wait until #14292 is completed.
The text was updated successfully, but these errors were encountered: