Sourcemaps
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, 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 needs access to the sourcemaps from your codebase. Sourcemaps can be sent to Highlight in your CI/CD process.
The Highlight 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 will use to send .map files. The default value is ./build.
The version of your current deployment. This is the same version string your provide as version to H.init(). This ensures that we're always using the same set of sourcemaps for your current bundle. The default value is the current Git hash.
To use the Highlight sourcemap-uploader , you need to be generating sourcemaps for your project. Exactly how to do this depends on your target environment and javascript configuration. Bundlers like babel, webpack, esbuild, or rollup all provide different ways to enable sourcemap generation. Refer to documentation for your specific bundler to generate production-ready sourcemaps or reach out if you need more help!
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.

