# Source Maps

BugSplat has the ability to convert uglified and minified JavaScript stack traces into function names and line numbers from the original source. You can upload [source map](https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Use_a_source_map) files to BugSplat during your build process by leveraging [@bugsplat/symbol-upload](https://www.npmjs.com/package/@bugsplat/symbol-upload).

In order to correctly unwind uglified stack traces, you’ll need to ensure that the filename of the source map matches the file name of the original source file. For instance, if your build process generates a file `main.153ee63b.chunk.js`, the corresponding source map file should be named `main.153ee63b.chunk.js.map`.

{% hint style="info" %}
Be sure to upload source maps for each released version of your application for best results.
{% endhint %}

If BugSplat is unable to convert the uglified stack trace back to the original source the **Debugger Output** tab will display diagnostic information from the BugSplat backend that will help you troubleshoot.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bugsplat.com/introduction/development/working-with-symbol-files/source-maps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.