All Collections
Advanced usage
See Javascript stack traces by applying source maps
See Javascript stack traces by applying source maps
Jordi Giménez avatar
Written by Jordi Giménez
Updated over a week ago

When building a Javascript app, sometimes the source code goes through a series of transformations, such as obfuscation (sometimes called "uglifying"), minification, or source-to-source compilation (or transpilation). This process makes the final code less readable, so a file called source map can be generated to find out the original names of functions, file names and line numbers in case you need to.

When you're debugging an application, you can use these source maps to map stacktraces, for example. In Bugfender, you will see a Mappings: Missing message. You can click on that icon to upload your source maps.

Here are the most common problems we have found when using source maps:

  • The source maps must match the version of the code. If you use different versions, some symbols will be missing and the file names and line numbers might not make sense.

  • Bugfender only accepts a single file, so you'll need to combine them during your build if you have multiple files. Most build systems already output a single file.

Did this answer your question?