Clojurians Log v2

@darwin Chrome Canary 64.0.3273.0, MacOS 10.12.6, Clojure 1.8.0, ClojureScript 1.9.946, dirac "RELEASE". Now I try it again I do notice a warning which is probably pertinent "We detected unexpected tools.nrepl library version in your nREPL server at <nrepl://localhost:8230>! The server reported version 0.2.12, but Dirac expected version 0.2.13"

i'm trying to figure out what is pulling in 0.2.12

that should be fine in this case, don't worry about this

there are not protocol differences between 0.2.12 and 0.2.13

oh, ok

then i saw no other warnings or messages

the thing worked in the sense that I could navigate to a .cljc file and set a breakpoint

and it stopped at the breakpoint

but it didn't show any of the locals in scope at that point and the stepping seemed a bit wonky

did you try the same thing in internal devtools? was it better (minus names demangling)

?

i've no idea what you're asking me

what do you mean by "the same thing"

you mean setting a breakpoint in some JS code?

did you try to set the same breakpoint in normal chrome devtools without using Dirac?

no

please try the same workflow, just to check if you would see the locals you are expecting to see there

are you talking about CLJS and cljs scope or JS & js scope?

What I mean is, I am not sure what should be possible in the built-in devtools

i didn't think it could set breakpoints in CLJS code or inspect scopes

you can, but you won't get some things dirac offers on top

also i guess that means i have to pull dirac out of my dependencies

for example demangling clojurescript-generated variable names

no, you don't have to pull dirac out, simply instead of dirac devtools open internal chrome devtools on your page

since recent chrome releases they even work side by side, but better to close dirac devtools window and use the intenal (bundled) devtools

okay so chrome internal devtools seems to have the local scope variables

ok, then something went wrong with dirac, I would need to see the code or maybe screenshots in the first step

in the beginning I thought you placed the breakpoint to a wrong place where you expected locals but your were stopped "elsewhere" than expected

using (js-debugger) should be precise, but using devtools UI could confuse real location

because your clicks to set breakpoints go through source mapping somewhere into generated javascript code and you might hit some problematic spot

please try to make two screenshots for me a) hitting the breakpoint in dirac devtools b) hitting it in the normal devtools

Ok. Can't do it now as I have to switch to some other work. But I'd be interested in having this work so next chance I get I will try and capture the two.

Thanks for taking an interest.

ok, np, ping me here anytime