Option to automatically delete source maps after upload

[yayapao]

For security purposes, we should not expose sourcemaps online. So a cleanSourceMaps configuration is good to autodelete sourcemaps after artifacts has been uploaded successfully.

[lforst]

We thought about adding this before in the webpack plugin we already had. For now, we consider this a bit out of scope as you can just delete source maps yourself after your build is complete and there is always the challenge for the Sentry plugin to know which files to delete - is it just the ones that the plugin uploaded or also the rest? Just some things to consider.

I will leave this issue open as it is a valid feature to think about.

[wtachau]

Here's what I ended up doing to delete sourcemaps after uploading (in the build script):

find <output dir> -type f -name '*.js.map' -delete
find <output dir> -type f -name '*.css.map' -delete
find <output dir> -type f -name '*.js' -exec sed -i -E 's/sourceMappingURL=[^ ]*\.js\.map//g' {} +
find <output dir> -type f -name '*.css' -exec sed -i -E 's/sourceMappingURL=[^ ]*\.css\.map//g' {} +

[kricsleo]

Deleting sourcemaps also means a lot to me. I prefer to delete all of them before deployment. If someone wants to keep them, they can disable this config and do the job as they want. But in most cases, deleting all sourcemaps would be a more common use case.

[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 🥀

[filiptammergard]

Nice @lforst! Can you please announce here when deleteFilesAfterUpload is available to use, and how to use it?

[lforst]

@filiptammergard I hope I don't forget :D

[lforst]

We released this in the newest version of the plugin! :)