This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-12
Channels
- # beginners (34)
- # boot (14)
- # cider (2)
- # cljs-dev (21)
- # cljsrn (1)
- # clojure (31)
- # clojure-android (10)
- # clojure-spec (12)
- # clojure-uk (3)
- # clojurescript (64)
- # cursive (31)
- # data-science (9)
- # datomic (27)
- # fulcro (11)
- # graphql (14)
- # jobs (1)
- # leiningen (1)
- # lumo (27)
- # off-topic (65)
- # om (2)
- # onyx (77)
- # pedestal (1)
- # re-frame (4)
- # shadow-cljs (6)
- # vim (1)
- # yada (3)
Hello, I read "JS-dependencies-in-practice" and am very interested in alternate ways to coexist with npm modules. I'm trying to understand how does shadow-cljs fit in existing build system? Right now I see it as an external application that kinda does everything with its own config files. I see that it also provides watcher and reloader. Does that mean it replaces figwheel or boot-cljs or lein-cljsbuild? Or maybe replace the whole lein/boot in the project?
Hi! I'm using shadow-cljs with the
guide for working with create-react-app
. There's a link to an issue there where @thheller talks about getting auto-reload working for recompiled cljs
files. They propose a sym-link solution there, which @thheller makes work - but how? Sorry if this is a noob question, I've been using shadow-cljs for literally 15 minutes