Open lilouartz opened 2 months ago
Hey @lilouartz would you mind letting us know why you want to disable debug id injection? This snippet is injected so that we can better associate the minified stack frames with the correct source maps to show you the unminified stack frames in the Sentry UI.
How do I disable this?
You can give our legacy source maps uploading strategy a try. This won't inject debug id snippets into your code but you'll need to more carefully set up source maps upload
Feels lame that I have to use something named "legacy" for what seems like a basic ask.
I gave you an alternative. Without having more context as to why you want to achieve this, we cannot prioritize further work.
Hey @lilouartz would you mind letting us know why you want to disable debug id injection?
At this time, we don't understand why this is a "basic ask".
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 remove the label Waiting for: Community
, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
I am having the same issue, the issue is Sentry config on vite is injecting an import to my web worker. We should have an ignore list or a way to prevent Sentry from importing on specified files.
@chadgauth you can use the sourcemaps.ignore
option to disable injecting the debugId snippet into specific files. Vice verca, you can also specify assets
to limit the injection of debugIds and source map upload to specific file paths (glob patterns work for both).
Note that once you do this, errors ocurring in the excluded files will not be source-mapped correctly.
Looks like Sentry injects this to every file:
How do I disable this?