Using source-maps cross projects in a micro-app setup

[n-smolders]

Problem Statement

We are running a micro-frontend setup at our company, and as such have configured a separate project in Sentry for each micro app. Using the webpack plugin to prepare and upload our source-maps to Sentry for each project.

Since our frontend is constructed of multiple micro-apps running on the same page, it happens quite often that a stack-trace passes through multiple micro-apps. This is where we encounter issues with unminifyi'ng code, because the source-map of that particular file in the stack-trace is part of another project then where the stack-trace originated from.

Solution Brainstorm

Allow uploaded source-maps to be used cross-project for better stack traces and issue resolution.

Product Area

Issues - Source Maps

[getsantry]

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

[scttcper]

What version of webpack and the webpack plugin are you using? Are you using debug ids with the sourcemaps? https://docs.sentry.io/platforms/javascript/guides/nextjs/sourcemaps/troubleshooting_js/artifact-bundles/