Fork me on GitHub
#shadow-cljs
<
2022-08-30
>
pmooser14:08:20

I see an error in the console every time I save my CSS file - CSS reloading used to work for me, so I'm not quite sure what this means. I'm using shadow-cljs version 2.19.9, and the error I get any time I save my CSS file is:

pmooser14:08:01

I don't know much about debugging in shadow-cljs but I'm not really able to get a breakpoint to stop there ...

pmooser14:08:17

Ok - I fixed it by removing: :preloads [shadow.remote.runtime.cljs.browser] from :devtools which I believe was given as a workaround for some other issue at some point in the distant past.

thheller15:08:57

yes, that is long dead

thheller15:08:57

although it still exists as an empty namespace. so not sure how that would be causing any issues?

thheller16:08:41

what is that supposed to do? I mean are you trying to do that would require demunging?

zimablue16:08:28

in development I'm trying to reconstruct partial function call stacks so that I can trace a complex library that I'm struggling to understand

thheller16:08:53

don't source map handle that?

zimablue16:08:03

so (.-callee (js-arguments)) is cool but it would be cooler if I could demunge the names

zimablue16:08:26

maybe, I don't really understand source maps, are they accessible/useful outside of chrome devtools? where should I read

thheller16:08:27

yeah, no clue. source maps won't help there

zimablue16:08:06

does source map have (clojure symbol from) (javascript symbol to) correspondences in a format I can digest in the REPL?

zimablue16:08:34

sorry I come from python/c# not web tech so my understanding of all this has some gaps

zimablue16:08:16

that might have been a stupid question, the answer I'm pretty sure is "yes", a better question might be if there's a useful example or library in clojurescript for parseing these .map files?

zimablue16:08:26

and I maybe answered that one, cljs.source-map seems to be what I'm looking for

jpmonettas18:08:01

> in development I'm trying to reconstruct partial function call stacks so that I can trace a complex library that I'm struggling to understand @zimablue maybe https://github.com/jpmonettas/flow-storm-debugger can help you there, you will have to add #trace tags to every form you are interested in but then you can use all the debuggers functionality, specially https://jpmonettas.github.io/flow-storm-debugger/user_guide.html#_call_stack_tree_tool

zimablue18:08:48

I'm not trying to step through it though, more like run an extended test with specific functions decorated and then poke around the generated data

zimablue18:08:53

I don't find debuggers super useful beyond a certain level of "lost" because there's just too much to step through and eg. you're only interested in the 58th function call, which is obvious to identify from the data but hard to specify as a condi breakpoint

zimablue18:08:59

maybe I just need to get better at debugging

zimablue18:08:36

would flow storm debugger help with that sort of workflow?