Are source maps cached?

[adamreisnz]

I have encountered some errors in Sentry in which the source maps weren't parsed and I could only see the minified source code. I think this is because our source maps (and minified code bundles) are hashed, so for each deployment they get a unique file name.

If someone still has a browser window open with the old code base, Sentry doesn't seem to be able to find the missing source map file.

Is that to be expected or is there some way Sentry could cache the source maps so we would always have access to non minified code via the dashboard?

[mattrobenolt]

I think what you're looking for us our releases. This should give you more information about that: https://docs.sentry.io/hosted/clients/javascript/sourcemaps/#making-source-maps-available-to-sentry

[adamreisnz]

Ah thanks, I didn't know I can upload sourcemaps manually. Cheers.

[adamreisnz]

Sorry, can I not just upload a source map via the dashboard? Is via the CLI the only way?

[dcramer]

Its not really a process that caters to manual effort. You need to upload a sourcemap with each change of the sourcecode (usually each release) so we focus on features that make the process of pushing those easier.

[adamreisnz]

Fair enough, I guess I was just looking to quickly upload it so I could test it, but it makes more sense to integrate it after a deploy step. I will play around with it a bit later today.

[adamreisnz]

@dcramer follow up question: how would I upload different source maps for different environments? Our apps usually run on a variety of different (sub) domains, hosted on different Firebase servers, for each environment (e.g. demo, staging, production).

Not only will the domains be different (which we can cater for by omitting the --url-prefix option from what I understand), but the actual source code and files will also be different, because we integrate our custom environment specific configuration files in our minified source code. This then of course results in a (slightly) different source map for each environment.

How do I consolidate this and properly set up source map support for the different environments for a particular release, without having to split the environments up into different sentry projects?

For now, I've resorted to excluding the configuration files from the bundles so that the core bundle remains the same for all environments, but it would be great if there's proper support for different source maps per environment.

[dcramer]

@adambuczynski you'd use unique filenames (e.g. put a version in the URL). You can either re-use them on the same domain, or simply upload one per domain (we do that at Sentry, e.g. for staging vs production).