This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-16
Channels
- # announcements (7)
- # babashka (1)
- # beginners (125)
- # bristol-clojurians (4)
- # calva (49)
- # cider (10)
- # cljs-dev (3)
- # clojure (102)
- # clojure-berlin (3)
- # clojure-czech (4)
- # clojure-europe (84)
- # clojure-france (29)
- # clojure-italy (2)
- # clojure-nl (26)
- # clojure-norway (5)
- # clojure-spec (4)
- # clojure-sweden (4)
- # clojure-uk (50)
- # clojurescript (3)
- # community-development (2)
- # conjure (19)
- # cursive (9)
- # datascript (4)
- # datomic (33)
- # fulcro (4)
- # off-topic (26)
- # parinfer (10)
- # pedestal (4)
- # quil (8)
- # re-frame (1)
- # reagent (20)
- # remote-jobs (5)
- # reveal (53)
- # sci (10)
- # shadow-cljs (37)
- # spacemacs (6)
- # sql (25)
- # tools-deps (24)
- # vrac (2)
- # xtdb (10)
👋 I’m trying to setup a REPL connection to a freshly created re-frame project from a lein template (using Turns out cider was defaulting to lein for running the REPL instead of shadow-cljs. After I’ve run lein new re-frame proj +cider
). I’m using spacemacs with clojure layer. After executing cider-jack-in-cljs
I get asked about shadow-cljs build, where I provide app
. The cljs REPL fails to start with an exception missing instance {}
with basically exact same stacktrace as in https://github.com/clojure-emacs/cider/issues/2812. From what I understand, the case from the issue applies to a situation where deps.edn is present. This, at least as far as I can tell, is not the case for the re-frame template. Has anyone stumbled upon an issue like this?lein watch
once, the option to choose between lein and shadow-cljs appeared during connection setup process.