This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-11-16
Channels
- # announcements (11)
- # beginners (184)
- # calva (91)
- # cider (68)
- # cljdoc (42)
- # cljs-dev (44)
- # clojure (228)
- # clojure-dev (1)
- # clojure-europe (3)
- # clojure-italy (4)
- # clojure-losangeles (6)
- # clojure-nl (9)
- # clojure-spec (73)
- # clojure-uk (19)
- # clojurescript (61)
- # core-async (6)
- # cursive (2)
- # datomic (11)
- # fulcro (28)
- # hyperfiddle (16)
- # leiningen (2)
- # luminus (3)
- # off-topic (19)
- # om-next (1)
- # re-frame (2)
- # reagent (12)
- # reitit (4)
- # ring-swagger (5)
- # shadow-cljs (14)
- # slack-help (6)
- # spacemacs (2)
- # tools-deps (40)
- # vim (15)
- # yada (4)
Hi! I'm currently learning Clojure(Script) and web development in general, and I'm interested in understanding the tooling. So far I've created a very small playground app and I'm using lein and figwheel-main. But I want to give shadow-cljs a try since it looks awesome. One question before I start actually porting stuff would be: I am depending on a library that has react as a dependency via cljsjs iirc. Does that pose a problem when switching to shadow-cljs? Or can I exclude those and get react into the project via node?
shadow-cljs ignores cljsjs. so you can install react/react-dom as an npm dependency and it will just work
is there an easy way in shadow-cljs watch
mode to expose the value of an environment variable to a value in cljs-land?
of course now I'm realizing that I only need env vars for local development, and then to derive everything from the url for the compiled js