Server-side source map support on elmah.io
Error: You cannot copy to the clipboard at window.copyTextToClipboard (https://foo.bar/bundles/sharedbundle.min.js:69:24978) at MyViewModel.n.copy (https://foo.bar/bundles/viewmodels.min.js:37:37385) at HTMLButtonElement.<anonymous> (https://foo.bar/bundles/sharedbundle.min.js:55:109467)
But what if you for some reason cannot publish the source map file to the webserver? Common reasons for this are:
- You publish your code inside a wrapper to run as an app on a mobile phone and want to keep the package size as small as possible.
There are probably other reasons too. With server-side source map support, we provide a way for you to upload your source map to elmah.io through the API. This way, your source map won't be public or included in your build output. Once elmah.io receives a bundled and minified stack trace, we automatically try to de-minify it using an uploaded source map.
Uploading source maps is easy either manually on the Swagger UI page, through an HTTPS call, or through one of our integrations. We currently support integrations for Azure DevOps, GitHub Actions, and Octopus Deploy. But anything able of invoking the upload source map endpoint can upload a source map to elmah.io.
Check out the documentation for more details about how this works and how to configure an upload as part of your deployment pipeline: https://docs.elmah.io/sourcemaps/.
elmah.io: Error logging and Uptime Monitoring for your web apps