I generated a source map for my advanced compiled production build and put it in production. However, it's not fully working - the browser recognizes the source map, and stack traces now include the right file names and line numbers, but the symbols/names are still mangled. Also, when I click on a file location, the source is empty. Any pointers?

@christian767 the original sources can't be resolved - that's all

you've either put them in the wrong place, or you didn't deploy them

ah, so the sources need to go out as well

I thought all the required information was embedded in the sourcemap

will deploying the sources help the browser resolve the names as well?

no source map just does mapping

you can't magically embed all that source 🙂

well you could include sourcesContent in the source map

I guess 🙂 Well, copying the sources over solved the navigation, but the symbols on the left are still garbled

@christian767 if you are debugging :advanced issues setting :pseudo-names true is very helpful since it makes the names actually somewhat readable

Ok, thanks. I'll try that. I expected that source maps would know to translate PZ to taoensse.timbre/log, but that's perhaps hoping for too much?

that might just be a limitation of the browser not doing that translation

the source map in theory contains all that info

but doing that translation is quite costly so browser probably just don't do it at that level

ok

yes, I thought that info was in the source map

:advanced also changes the code in pretty dramatic ways .. so it might just not be possible to map it back

for debugging use :pseudo-names (with or without source maps)

does that affect build size dramatically?

yes

definitely don't deploy that. only use it for debugging.

ah, ok

I'm trying to improve insight into production faults 🙂

thanks for your input @thheller @dnolen! Much appreciated

btw, does anyone know of tools for parsing source maps on the JVM? Something like this, just for the JVM: https://github.com/mozilla/source-map/

yeah, there is something in the closure compiler for that. its just not well documented. see https://clojureverse.org/t/server-side-decoding-of-javascript-sourcemaps/1591/3?u=thheller

👍

@thheller where does com.google.debugging.sourcemap come from? com.google.javascript/closure-compiler-unshaded?

that screams monad to me, but afaik monads are not the clojure way, so what would be the clojure way ?