Open thinkocapo opened 1 day ago
Auto-routing to @getsentry/product-owners-settings-integrations for triage ⏲️
@thinkocapo we're always open to community contributions and public integrations through integrations platform. Is there something in integration platform missing that we can add and help cases like this? Other than that creating a ticket on Shopify side makes sense to me.
cc: @Dhrumil-Sentry in case there's already a partnership I'm not aware of.
Problem Statement
Sentry Customers that use Shopify (e.g. shopify ui-extensions) are often unable to obtain Sourcemaps for the code+app built by Shopify.
These customers have a
shopify
cli tool for building and deploying but it does not provide an option for obtaining the sourcemaps.Shopify's recommended error-handling with Sentry. Shopify's shopify cli
There's a worker.js file that's part of Shopify code and not the customer's app, it's the Worker that shopify creates for running the extensions. The worker.js file we see in sourcemaps was deployed with the Vite Sentry plugin when customer ran a build with shopify-cli, but when customer deployed the extensions with the shopify-cli the build and deploy were on Shopify's side and customer was not generating new sourcemaps.
Solution Brainstorm
In order to deminify these stacktraces from shopify, I think the easiest path forward here is for Shopify to add a
shopify
cli option for obtaining the sourcemaps. Then, the Sentry Customer can upload the sorucemaps to Sentry. I opened this GH Issue with Shopify requesting that feature.Integration - Sentry & Shopify could form a partnership and integration so that Shopify could send the sourcemaps to Sentry, via an integration, for the right release.
Product Area
Settings - Integrations