I'm not sure I understand your question?

source maps map JS code back to CLJS, that is correct

they are generated during compilation

by default they are disabled for release builds, you can enable them by setting :compiler-options {:source-map true}

I'm not quite sure what the point of logrocket for development is?

logrocket is pointless for local development on my computer. It captures user sessions in production. If the encounter a js error, without further information (source maps) for us, the error it gives us is compressed js. I attempted to give LR source maps according to there instructions, and now it tells me the JS file where the error happened, but i'm hoping i can get it to tell me the cljs file and line number.

which source map did you give them? since the above is at most from a development build?

it is not from a release build. I assume you are not serving your users development builds?

> it is not from a release build. I assume you are not serving your users development builds? I'm not. I did a release then uploaded that source map. then i started my shadow server locally and LR is tracking that session. Likely i need to do a release, upload that, then run that release locally.

I'm still lost how this all fits together

> then i started my shadow server locally and LR is tracking that session.

hmm?

why is LR involved in development?

you generate a release build. it generates a matching .map file, that ONLY matches that JS output.

if you run any other JS, it won't match and give you now proper results

so then running the dev build locally against those maps is pointless

so I'm still unsure what you are trying to do exactly

Thanks for the help. This largely isn't a shadow question. I was more asking if people using error reporting tools for production apps were able to get those tools to report the exact line the error happened at in the original cljs file. If everyone said no then i would assume there was some huge obstacle there. What i want is to log into logrocket, view a production user session, and if they had a js error, have log rocket tell me where in the cljs file the issue happened. If you don't upload sourcemaps, what it tells you is the location in the js minified file, because thats all it has. In my attempt to develop on this feature, i'm trying to use a locally running version of the app on my computer. LR has no probably tracking that session, just like i can track any session. I think my mistake is thinking the release build would be identical to what the shadow server build was producing. I should just run the release locally and see if its working as expected. The alternative is that i configure LR, upload the assets, and wait for a staging build. That has like a 15 minute turn around time. so if for some reason the configuration is wrong, it takes a long time to adjust.

what you can and should do is version your javascript

you have several option to do that https://shadow-cljs.github.io/docs/UsersGuide.html#_cacheable_output

and you need the EXACT output of the exact build, not a different build. the same map and matching JS file

yes, you cannot just run release locally again. that will give you a different build

if you version it from the beginning you'll have an easier time figuring out which JS caused the problem

and then just download it yourself and use it

do not do a rebuild

so you'll have a +

if the files match you should get proper traces

that makes sense, I think your right that would be necessary for this to work properly. If done correct, is it possible to get the same error report we get locally from an error that happened to a user using the minified release?

I don't know what you mean by that

if you use the same files you get the same error

if you figure out what it was in the first place 😛

Let me try to explain again, this is useful for me because its possible i'm barking up the wrong tree. Logrocket downloads the js file from a user session that we have allowed it to track, If an js error happened in that session, LR will show where in the js file it downloaded that error was. In a minified file that looks like this:

adow$provide[0]=function(T,I,ia,ha){var E=Object.getOwnPropertySymbols,F=Object.prototype.hasOwnProperty,g=Object.prototype.propertyIsEnumerable;ia.exports=function(){try{if(!Object.assign)return!1;var h=new String("abc");h[5]="de";if("5"===Object.getOwnPropertyNames(h)[0])return!1;var k=

the line number in the minified file, and the accompanying text (above) isn't useful for debugging the issue. So i need to unminify it, and then map it back to the cljs. I assume that's possible, but i haven't read a tutorial on it, i haven't seen it done, and yet it would seem like an obvious thing to want. If this works out, maybe ill write the tutorial, then discover there are like 10 of them already, i just failed to find them.

ok stop

there is your mistake

you don't do any of thjat

assuming the code above sits in a app.v1.js file and you have uploaded a app.v1.js.map file to LR, you should get proper stacktraces already

thats it. nothing else to do

> So i need to unminify it, and then map it back to the cljs.

that is literally what the source map is for

you don't do anything, it just works

only problem is if files don't match

or you try a development build and somehow map that to a release build

that will never work

I agree. My hope was that the only thing i had to do was upload the source maps. Thanks a ton, i'm pretty confident on what i have to do now.

the screenshot you posted above was some development build

yeah

since a release build doesn't contain any cljs-runtime/ code

the reason you need versioning is to ensure the files match

if you run a shadow-cljs release app and produce just a app.js

and then do that again, there is no way to map anything

since it won't be clear what code was used

yep, total makes sense. 🙂 Thanks for your patience and support.