This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (17)
- # boot (7)
- # cider (1)
- # cljsrn (4)
- # clojure (22)
- # clojure-austin (19)
- # clojure-canada (1)
- # clojure-dusseldorf (1)
- # clojure-greece (3)
- # clojure-russia (19)
- # clojure-spec (46)
- # clojure-uk (23)
- # clojurescript (17)
- # core-async (7)
- # cursive (13)
- # dirac (66)
- # kekkonen (1)
- # lein-figwheel (2)
- # om (1)
- # onyx (2)
- # re-frame (1)
- # reagent (1)
- # specter (2)
Hi! I'm trying to get Dirac working. Hitting
Unable to resolve backend-url for Dirac DevTools. target-url=.
OK, I've launched chrome with
google-chrome --remote-debugging-port=9222 and now the Dirac devtools doesn't complain.
However, when I type
(dirac! :join) in the REPL, it says `Your session joined Dirac (ClojureScript). The specific target Dirac session will be determined dynamically according to current matching strategy.
No connected Dirac session is "most recent Dirac session".`
@danielsz: yes, that works as expected, please read
(dirac! :help) and
(dirac! :help :join)
are you aware of this page? https://github.com/binaryage/dirac/blob/master/docs/integration.md
depends on your system I guess, go to <chrome://extensions>, and see “keyboard shortcuts” in bottom right
My next problem is that
(dirac! :ls) tells me: No Dirac sessions are currently available. Connect with at least one Dirac REPL to your nREPL server.
do you have dirac agent running? do you have Dirac DevTools open, switched to console, switched to dirac prompt and connected to the agent?
I have the latest dirac version, but the welcome message doesn't appear. Should I restart the browser?
Only these messages: Installing Dirac Runtime v0.6.0 and enabling features :repl util.js:206 Installing CLJS DevTools 0.7.0 and enabling features :custom-formatters :sanity-hints
Also I would recommend using the Canary, I don’t test Dirac with older Chrome versions, and chances are it simply breaks with older chrome
Okay, thanks for the tip. I'm doing some progress with my current version of Chrome but I'll switch if I can't get the full experience.
btw. you can open internal DevTools to debug Dirac DevTools, simply use standard keyboard shortcut for opening devtools while your Dirac DevTools window is focused. You might spot there some errors.
Cool. I managed to join the dirac session. Evaluation of simple forms works. However,
in-ns my.namespace results in an infinite loop :face_with_rolling_eyes:
I've restarted everything, but this time I switched to my namespace with
(ns my.namespace) and this did the trick.
With the Canary channel, do you also need to launch chrome with remote-debugging or is it on by default?
And by the way, the awesome thing with boot-cljs-devtools is that most configuration is done behind the scenes.