Some issues don't use sourcemap, some do


#1

Hello! :wave:

I recently enabled Sentry for JavaScript in a production environment. Before I start, amazing product! :tada:

I have noticed that the majority of issues being reported don’t use the sourcemap, but a minority of issues do.

We have a number of asset bundles built with webpack that are all bundled under the same config.

Here is a small bundle example: https://gitlab.com/assets/webpack/raven.43c8560e3ef98ef162fa.bundle.js

Which declares //# sourceMappingURL=raven.43c8560e3ef98ef162fa.bundle.js.map

Here is it’s sourcemap:
https://gitlab.com/assets/webpack/raven.43c8560e3ef98ef162fa.bundle.js.map

But, I’ve seen issues for errors within this bundle and they don’t seem to use the sourcemap.

I’m certain I’m doing something wrong, but we just can’t work out what exactly.

Here is our current webpack config: https://gitlab.com/gitlab-org/gitlab-ce/blob/1142d6ba482223f01aa89a523ad3769411807e69/config/webpack.config.js#L200

Sound familiar to anyone?

Thanks for reading! :heart:


#2

I’d have to see a sample issue in order to understand why source maps are not being applied. If you could share some screenshots, that could be helpful.