Luca Forstner

As a workaround you can set `disable: true` for when you do dev builds.

This seems to be related to https://github.com/getsentry/sentry-javascript-bundler-plugins/issues/345 which is a downstream issue in the unplugin package: https://github.com/unjs/unplugin/issues/323 The current plan is to move away from `unplugin` but it will require...

The recommended workaround for now is to use Sentry CLI instead of the webpack plugin.

@jobejas No there is not but you can use the `allowUrls` option in `Sentry.init()` which achieves similar effects.

@owenjs I don't think any bundler loads .env files by default. I also don't think our example is wrong. If you wanna use vite's way of accessing environment configuration you...

Hi, thanks for writing in and doing the research! I don't think we will fix this soon. I recommend using Sentry CLI instead to upload source maps for the time...

If you set `sourcemaps.disable` on the latest version of the plugin, it will not inject debug ID snippets but you will have to resort to the `release.uploadLegacySourcemaps` option for sourcemaps.

@0Calories mind taking a look?

Hm, I am not sure how I can reproduce this. Would you mind sharing a small reproduction example (repo we can pull or stackblitz or similar) so we can debug...

@pirey none of that code is in our package. I wouldn't know how to change that tbh. I'd need reproduction.