This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-23
Channels
- # announcements (2)
- # beginners (150)
- # calva (59)
- # cider (10)
- # clj-kondo (63)
- # cljs-dev (15)
- # cljsrn (34)
- # clojure (127)
- # clojure-dev (16)
- # clojure-europe (12)
- # clojure-italy (18)
- # clojure-nl (6)
- # clojure-russia (3)
- # clojure-uk (23)
- # clojurescript (18)
- # clojutre (15)
- # clr (2)
- # cursive (3)
- # datomic (26)
- # duct (6)
- # fulcro (9)
- # graalvm (3)
- # joker (9)
- # lambdaisland (1)
- # off-topic (12)
- # om (1)
- # pathom (29)
- # re-frame (16)
- # reagent (2)
- # shadow-cljs (57)
- # slack-help (2)
- # spacemacs (45)
- # sql (20)
- # xtdb (3)
- # yada (3)
I am seeing this error when I try to connect with cider-connect-cljs
after choosing shadow-select
. I don't believe it is related to the changes mentioned above from this weekend--I get an identical error with the latest stable CIDER as with the latest snapshot.
Frankly, I don’t recall whether we’ve tried starting a ClojureScript REPL outside of some project and it seems you’re doing exactly this.
For something like shadow this doesn’t make much sense as you won’t have build files and the shadow dep won’t be injected in your project.
Actually I didn’t read very well your stacktrace - seems you’re just doing connect, not jack-in, so this should work, but you did invoke it outside of a project dir which is probably the problem.
https://github.com/clojure-emacs/cider-nrepl/blob/9020b61672121725a3a8a9283fe2caaf1545cf20/src/cider/nrepl/middleware/test/extensions.clj#L16 this breaks the evaluation order of =, so effects that happen from more happen before effects from expected