symbolic

Some direct links if folks are interested about how it works: scope extraction is in js-source-scopes, which uses SWC behind the scenes: https://github.com/getsentry/js-source-scopes The more user friendly and performant version of it is available as part symbolic: https://github.com/getsentry/symbolic/tree/master/symbolic-s... Which is also exposed to Python so you can use it from there if you need: https://github.com/getsentry/symbolic/blob/master/py/symboli... Happy to answer questions :)

Sentry is using it to help their Python backend to process crash reports: https://github.com/getsentry/symbolic

I think folks might find Sentry’s use of Rust interesting. Sentry is quite invested in Python on their backend, but needed additional performance mostly related to symbolication of crash reports. So they have a Rust symbolication library with Python bindings giving them the best of both worlds for their app. https://github.com/getsentry/symbolic

It’s actually a simplifiedversion of what we do. We deal with debug information files and write custom cache files thag look similar to that. https://github.com/getsentry/symbolic/tree/master/symcache/s...

> What if instead of that you’d actually compile all JS files once to some sensible format that would allow you to do lookup of variable in any scope? An enormous amount of javascript and sourcemaps we are dealing with are one hit wonders and/or need fetching from external sources. We have no impact on the format of the data there and as mentioned converting it once into a different format does not at all help here. > I bet you don’t need full debug info as in complete DWARF data. Correct, which is why as part of making processing of iOS symbols faster we wrote our own file format that we can efficiently mmap. It's 10% of the size of the average DWARF, gives us all the information we want without parsing or complex processing (https://github.com/getsentry/symbolic/tree/master/symcache). The reason I'm writing this is because as you can s