This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-19
Channels
- # bangalore-clj (1)
- # beginners (8)
- # boot (102)
- # cider (1)
- # clara (14)
- # cljs-dev (2)
- # cljsrn (2)
- # clojure (49)
- # clojure-poland (3)
- # clojure-russia (4)
- # clojure-serbia (1)
- # clojure-spec (5)
- # clojure-ukraine (1)
- # clojurescript (181)
- # core-async (4)
- # cursive (2)
- # datomic (7)
- # dirac (34)
- # figwheel (3)
- # fulcro (21)
- # hoplon (5)
- # om (1)
- # parinfer (4)
- # planck (27)
- # re-frame (30)
- # reagent (11)
- # rum (6)
- # shadow-cljs (22)
- # spacemacs (4)
- # unrepl (26)
@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"
the thing worked in the sense that I could navigate to a .cljc file and set a 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)
please try the same workflow, just to check if you would see the locals you are expecting to see there
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
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