LogLevel was removed, but is referenced from NestJS-Sentry package

[jacoblb64]

• [x] Review the documentation: https://docs.sentry.io/
• [x] Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• [x] Use the latest release: https://github.com/getsentry/sentry-javascript/releases
• [ ] Provide a link to the affected event from your Sentry account

Package + Version

• [ ] @sentry/browser
• [x] @sentry/node @ 6.17.2
• [ ] raven-js
• [ ] raven-node (raven for node)
• [x] @ntegral/nestjs-sentry @ 3.0.7
• [x] @nestjs/core @ 8.2.6
• [x] node @ 14.18.0
• [x] typescript @ 4.5.5

Description

Saw this build error when updating to the latest Node SDK version and wanted to flag the probable cause of folks using this export, and encourage the Sentry team and maintainers of the NestJS integration package to work together toward a resolution.

Relevant discussion in this closed issue https://github.com/getsentry/sentry-javascript/issues/4449, and was removed in PR https://github.com/getsentry/sentry-javascript/pull/4317.

LogLevel is used in the basic getting started section of ntegral's popular NestJS wrapper for Sentry: https://github.com/ntegral/nestjs-sentry.

What would the Sentry team recommend using instead? Or is this solely the responsibility of the NesJS integration to solve?

[lobsterkatie]

Hi, @jacoblb64, thanks for writing in!

The Nest SDK is community-supported, so they're the best folks to help with this; I'd suggest opening a similar issue in their repo. That said, if questions come up as you're working with them there, feel free to point them in this direction and we'll be happy to offer advice where we can.

Cheers!

[jacoblb64]

Sounds good, will chat with folks there, appreciate the help!