Luca Forstner

It might be you being used to the v1 api of the webpack plugin which had the `release` option. We have types nowadays (even in JS) so I think printing...

Hi, when building `saas` the source maps that were generated when you built `core` should be picked up automatically. You generally don't have to add `core` to `sourcemaps.assets` - in...

Are the sources from `core` included in the output source maps for `saas`? If not, it is likely a configuration issue on your end with vite. If they are, remove...

Hi, we're not doing any custom network things/tls in the plugins so this is likely an issue with your setup.

Hi, what I recommend doing here, and I do this in my side project too, is the following: ``` setCommits: { repo: 'lforst/my-repo', commit: process.env.VERCEL_GIT_COMMIT_SHA, previousCommit: process.env.VERCEL_GIT_PREVIOUS_SHA, }, ``` Note...

Idea on how to fix this: We try-catch the `setCommits` command and log a warning/error with instructions on how to fix this. Actually.... Not sure yet if we should keep...

> Since foo.js keeps changing on every build, thedebugId generated for main.js is affected Can you explain why changing foo.js affects the hash of main.js? But in general you're probably...

Hi, please refer to this guide to troubleshoot your source maps: https://docs.sentry.io/platforms/javascript/sourcemaps/troubleshooting_js/legacy-uploading-methods/ I also recommend upgrading the version of your self-hosted instance.

Thanks for writing in! Unfortunately the dependencies come from the `unplugin` package and I currently don't know how I would sustainably resolve this issue. We're open to any suggestions! Short...

Yes sorry. This shouldn't be closed. Plan is still to move away from unplugin.