This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-04
Channels
- # aleph (10)
- # announcements (2)
- # babashka (2)
- # beginners (101)
- # calva (17)
- # cider (11)
- # clara (6)
- # clj-kondo (25)
- # cljsrn (33)
- # clojure (181)
- # clojure-dev (15)
- # clojure-europe (3)
- # clojure-italy (4)
- # clojure-nl (8)
- # clojure-uk (22)
- # clojurescript (111)
- # clojutre (58)
- # cursive (31)
- # data-science (1)
- # datomic (10)
- # emacs (6)
- # ethereum (1)
- # fulcro (20)
- # graalvm (3)
- # jackdaw (5)
- # leiningen (5)
- # off-topic (31)
- # re-frame (2)
- # reitit (10)
- # shadow-cljs (9)
- # spacemacs (16)
- # sql (8)
- # tools-deps (16)
- # vim (17)
Random newb question (not sure if this is the right place): I'm getting the following error when launching a CLJS project using Shadow-CLJS (both from CIDER and from the CLI): No Clojure project was detected. The refactor-nrepl middleware was not enabled
. Got some help from the #shadow-cljs folks and tracked it down (I think) to this line in refactor-nrepl
: https://github.com/clojure-emacs/refactor-nrepl/blob/master/src/refactor_nrepl/core.clj#L65. Obviously, looks like Shadow-CLJS is not a supported project type (i.e. shodow-cljs.edn
). The thing that confused me is there is an issue (resolved) in the refactor-nrepl
issues list referring to Shadow-CLJS (specifically about using strings within the require
form) so it appears folks are using shadow with refactor-nrepl
. Does refactor-nrepl
expect the shadow project file to be named something else or am I missing something?
one thing you could do is put a project.clj
file in the project. just leave it empty
true true.
Better way (and the reason that a shadow-cljs
issue probably exists) is deps.edn
. I'll move to that. Seems like the best path forward.