Should I continue reading?
If you publicly deploy sourcemaps with your application then you do not need this guide. This guide is for applications that don't ship sourcemaps with their application.
When debugging an error in highlight.io, it might be useful to get a stack trace from the original file in your codebase (rather than a minified file) to help understand what is going wrong. In order to do this, highlight.io needs access to the sourcemaps from your codebase. Sourcemaps can be sent to highlight.io in your CI/CD process.
Sending Sourcemaps to highlight.io
The highlight.io sourcemap-uploader can be used during your CI/CD process. Here's an example of using it:
The API key for your project. You can find this in the project settings.
The path that highlight.io will use to send
.map files. The default value is
The version of your current deployment. Please provide the same version value as the value you provide for
version in H.init(). This ensures that we're always using the same set of sourcemaps for your current bundle. If omitted, sourcemaps are uploaded as
unversioned (make sure H.init() does not have a
version option provided).
Electron App Sourcemaps
Although your electron app configuration may vary, many will chose to use webpack to generate sourcemaps. Refer to the general webpack sourcemap documentation as well as this useful reference to configure your build.