This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-15
Channels
- # announcements (8)
- # beginners (65)
- # calva (25)
- # cider (11)
- # clj-kondo (9)
- # cljsrn (14)
- # clojure (103)
- # clojure-europe (15)
- # clojure-greece (1)
- # clojure-italy (28)
- # clojure-nl (39)
- # clojure-spec (9)
- # clojure-uk (28)
- # clojuredesign-podcast (37)
- # clojurescript (56)
- # cursive (41)
- # data-science (10)
- # datomic (25)
- # duct (1)
- # emacs (1)
- # events (3)
- # figwheel-main (7)
- # fulcro (9)
- # graalvm (7)
- # graphql (10)
- # jobs (2)
- # nrepl (17)
- # off-topic (40)
- # quil (12)
- # reitit (11)
- # remote-jobs (5)
- # rum (2)
- # shadow-cljs (387)
- # sql (22)
- # tools-deps (8)
- # vim (26)
- # xtdb (47)
- # yada (9)
Anybody know should this work or how CIDER tries to detect Shadow-CLJS projects? Asking before reading the source.
I'll report here also that I was using my own forked clojure-mode that was old enough not to contain shadow-cljs files
I’ve seen this before. Is it possible the warning is from refactor-clj which doesn’t recognize shadow cljs as a project root. Does everything still work? Possible to just remove refactor
how about just do https://github.com/thheller/shadow-cljs#quick-start and switch to node-script
ah, i think shadow and CIDER don't play nice with node-script. But i don't remember the reason