Deprecation Warning for disableLogger and others should show turbopack solutions

[paradoxloop]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

10.32.1

Framework Version

NextJs 16.1.1

Link to Sentry event

No response

Reproduction Example/SDK Setup

The deprecation warnings during nextjs build show webpack options but not turbopack options. It would be better if it told me what the replacements in turbopack are given this is now the nextjs default.

[@sentry/nextjs] DEPRECATION WARNING: disableLogger is deprecated and will be removed in a future version. Use webpack.treeshake.removeDebugLogging instead.
[@sentry/nextjs] DEPRECATION WARNING: reactComponentAnnotation is deprecated and will be removed in a future version. Use webpack.reactComponentAnnotation instead.
▲ Next.js 16.1.1 (Turbopack)
- Environments: .env
- Experiments (use with caution):
  · clientTraceMetadata

Steps to Reproduce

Build nextjs with disableLogger used in sentry config

Expected Result

NA

Actual Result

NA

Additional Context

No response

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear]

JS-1431

[s1gr1d]

Hello and thank you for writing in!

The options in the log message are from the Sentry options, so you will see the message if you use those options in Sentry (independently from the used build tooling). For example, reactComponentAnnotation is only available with webpack (see docs here). Tree-shaking is also a webpack-only feature: https://docs.sentry.io/platforms/javascript/guides/nextjs/configuration/tree-shaking/

We might need to change the log message to explain that a bit better. There won't be a replacement.

[paradoxloop]

thanks @s1gr1d and @chargome

[github-actions]

A PR closing this issue has just been released 🚀

This issue was referenced by PR #18769, which was included in the 10.33.0 release.