Inject release SHA only to one output JS file about sentry-javascript-bundler-plugins HOT 2 CLOSED

Hi, you don't have to use the plugin's injection mechanism. You can simply pass in a release value yourself. For the debug ID mechansim of associating source maps, injection into every file is a necessity, we cannot get around that. The injection should be deterministic so the hash should only change when stuff is actually changing.

from sentry-javascript-bundler-plugins.

Hi @lforst , thank you for the explanation. I didn't realize the solution is that simple – explicitly setting the release name in vite.config.mts, and in the app code where we call Sentry.init().

It works wonderfully – vendor.js is not invalidated, errors are assigned to the release name, source maps are uploaded for the release name ✅

So basically, the code injection is a useful default to save us a few lines of config, by setting the release name during runtime. But we can just as well do it explicitly during build time 👍

Suggestion: there could be a brief mention in docs – that disabling injection and setting release name explicitly is useful in case we want to the code-splitting.
Otherwise it truly does mutate the vendor.js, and change its fingerprint, when there were no changes to its content.

from sentry-javascript-bundler-plugins.