Automatically turn on source maps generation

[lforst]

• How to do safely so we don't end up publishing user code by accident?
• Maybe just add some warnings + instructions?
• Auto remove source maps after upload?

[HazAT]

I think if someone goes as far and adds the plugin - they want source maps.

For those people where the wizard adds it - it's also fine.
This is not an issue and we don't need to be overly careful with it.

The countet argument is, without source maps - Sentry is more or less useless.

[lforst]

I want to be careful especially with the move towards Next.js server actions and all. We could be publishing serverside source code that contains secrets. But yea I wanna do this too.

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[timfish]

• Auto remove source maps after upload?

I think this would be key. If you force enable source maps, they should not end up in the output.

I've seen production Electron apps that have shipped source maps and this is almost always unintentional!

[s1gr1d]

Related to this issue: getsentry/sentry-javascript#13993

If no source map settings are set, we will enable 'hidden' source maps.

This issue can be closed.