If you 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; contact firstname.lastname@example.org to get access to this.
The path that Highlight will use to send .map files. The default value is ./build.
The version of your current deployment. This ensures that we're always using the same set of sourcemaps for your current bundle. The default value is the current Git hash.