Using source-maps across projects

[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.

edit from @smeubank PM @ Sentry

I would modify this to a request to have source maps which are only tied to an organization, and can be used across projects regardless of MFE. Project is a sentry abstraction to some extent.

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/

[smeubank]

I would modify this to a request to have source maps which are only tied to an organization, and can be used across projects regardless of MFE. Project is a sentry abstraction to some extent.

We'd probably need some evolution of debugIds/artifact bundles, and there's be some tax to pay to look up. That being said that kind of work is not planned at all.

@loewenheim do you recall conversation around debugIds and making them also decoupled from projects?

Short term solution: upload source maps for each relevant project related to the MFE.

[n-smolders]

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/

We are using webpack@5.94.0 and @sentry/webpack-plugin@3.0.0
Our source files have debugIDs injected into them allong with the dns metadata. Source files belonging to the same project get correctly unminify'ed. Its only the files outside the project where source-maps cannot be applied correctly.

I would modify this to a request to have source maps which are only tied to an organization, and can be used across projects regardless of MFE. Project is a sentry abstraction to some extent.

Do I need to edit the original post for this or is this an internal memo

[getsantry]

Routing to @getsentry/product-owners-ingestion-and-filtering for triage ⏲️