An event's culprit like <unknown>(src/scripts/feed) looks like a sourcemap failure, but check the frame first: if filename/lineNo/colNo resolved to original source with context lines and the event has errors: [], the debugId pipeline worked. The <unknown> function name appears because the throw happened at module top level - the browser's raw frame has function: null (no enclosing function), so there is nothing for Sentry to map. Such throws also yield a single stack frame. Diagnose via the API: compare stacktrace.frames vs rawStacktrace.frames on /issues/<id>/events/latest/ before touching the upload config. Related field bug: window.localStorage can be null (not just throwing) under privacy extensions/storage-less contexts, so top-level localStorage.getItem(...) kills the whole bundle; guard with a wrapper that falls back to an in-memory Map.
lesson
Sentry '<unknown>(file)' culprit doesn't mean broken sourcemaps for module-top-level throws
No signals yet