Source maps

I’m wondering about this statement:

"To provide inline code snippets we also require the map file to point to publicly accessible unminified source files. If these are not available decoding can still succeed but no inline code will be displayed with the stack trace”

Is this really true? The source maps contain the actual source, do they not? Why would you need the original source files as well? For modern javascript apps, this is hardly realistic as they can have 100s-1000s of files.

One other question, we use fingerprinted js files, so everytime we deploy the url will be different. Will the older ones eventually fall off of https://app.raygun.io/settings/xxxxxx/jssymbols or do we have to clear them manually? As it stands we'll probably be adding 10-20 different versions of sourcemaps per day. I'm wondering if we're going to break something by doing this.

---

Hi Aaron,

At the moment inline sources are not utilized by our source mapping process. This is something we hope to develop support for in the next few months.

Files uploaded to the source map center are currently retained indefinitely. While we haven't seen any issues with large numbers of files in there you can clear them out either manually or with an API call to keep things manageable.

You can use these API calls to manage the source map center:

DELETE https://app.raygun.io/jssymbols/[appId]/all - clears all uploaded files in the source map center

DELETE https://app.raygun.io/jssymbols/[appId]?url=[URL of file]&url=[URL of another file] - clears specific files based on their URL

GET https://app.raygun.io/jssymbols/[appId] - gets a list of all files in the source map center (useful if you wish to delete specific sets of files)

All use the same authentication methods as the upload call (auth token or basic auth).

Hope that helps!

Best regards,
Alex

---