[Next.js] Log a more useful warning than "Cannot initialize SDK with debug option using a non-debug bundle" when disableLogger: true

[lforst]

Description

The great founder of Sentry was confused by this and I think with good reason. We should log something more descriptive.

[lforst]

@a-hariti maybe something for you to look at!

[timfish]

It might also be a nice addition to only strip debug messages in production builds. I can't think of a reason why you'd want to do this in dev mode.

[a-hariti]

so what's the ideal DX in your opinion @timfish ?

[timfish]

In an ideal world, users shouldn't need to think about this 🤔

I think it would be improved a lot if we:

• Never strip debug messages in development mode
• Log a more helpful next.js specific message when debug is enabled in production mode

If I'm being picky, I'm not a huge fan of disableLogging as an option name. It's not describing what it does and negative options always make me think twice about what they're actually doing. What does disableLogging: false do? It does not enable logging!

Something like stripDebugMessagesFromProductionBundle is laughably long but also descriptive of what it's actually doing.

[lforst]

If I'm being picky, I'm not a huge fan of disableLogging as an option name.

I had the same thought and I was the genius coming up with that name.

[timfish]

Do we need to change anything here before v9?

If we change disableLogging it is probably used enough that we'd need to deprecate it for v9 and remove it in V10?

[lforst]

Don't think so. Changing the option name will not make it into v9 in any case.