This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-27
Channels
- # announcements (8)
- # architecture (3)
- # aws (18)
- # beginners (96)
- # bristol-clojurians (3)
- # calva (15)
- # cider (7)
- # clj-kondo (8)
- # clojure (135)
- # clojure-denmark (1)
- # clojure-dev (14)
- # clojure-europe (37)
- # clojure-italy (9)
- # clojure-nl (14)
- # clojure-sanfrancisco (1)
- # clojure-spec (1)
- # clojure-uk (54)
- # clojurescript (27)
- # core-async (243)
- # cursive (28)
- # data-science (6)
- # datomic (33)
- # fulcro (25)
- # graalvm (24)
- # hoplon (2)
- # instaparse (12)
- # jackdaw (1)
- # java (21)
- # juxt (12)
- # meander (10)
- # nyc (4)
- # off-topic (6)
- # om (3)
- # pathom (17)
- # perun (1)
- # re-frame (29)
- # reitit (4)
- # rum (3)
- # shadow-cljs (119)
- # spacemacs (31)
- # xtdb (14)
@dpsutton I have the cider-jack-in-cljs
repro steps that cause selecting clojure-cli
(when using shadow-cljs + deps.edn) to fail.
The repository is at https://github.com/Quezion/re-frame-react-native/tree/demo-cider-deps-clj-err ; you'll need npm to do execute a couple npm install.
I've included the repro info at https://github.com/Quezion/re-frame-react-native/blob/demo-cider-deps-clj-err/cider-repro.txt
The root of the error is why shadow.cljs.devtools.server.runtime/get-instance!
is failing though I can't say why.
(This is a followup from #shadow-cljs the other day: https://clojurians.slack.com/archives/C6N245JGG/p1582604733081400 )
I do want to note that running M-x cider-jack-in-cljs -> shadow-cljs
works just fine so it's not like this is stopping development.
Happy to provide more info if useful. I got the same errors when testing on both CIDER 0.21 and 0.24.
I can't guarantee this isn't PEBCAK on my part; it probably is if there's an existing repo that works with this flow
@quest Might be a better idea to file some ticket, so this won’t slip between the cracks here.
Does anybody use clj-refactor? I’m trying to find usages in cljs code, call the command, then the message is shown
To perform this op the project needs to be evaluated.
Analyzing a large project might take a while: hit C-g to abort.
(Set cljr-warn-on-eval to nil to analyze the project without warning)
Do you want to proceed? (y or n) y
I press y
and nothing happens
No messages in Messages buffer, nothing