This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-10
Channels
- # 100-days-of-code (2)
- # adventofcode (188)
- # aleph (3)
- # announcements (2)
- # beginners (76)
- # boot (3)
- # braveandtrue (49)
- # cider (82)
- # clara (15)
- # clojure (101)
- # clojure-europe (4)
- # clojure-india (3)
- # clojure-italy (26)
- # clojure-kc (1)
- # clojure-nl (4)
- # clojure-norway (1)
- # clojure-russia (5)
- # clojure-uk (33)
- # clojurescript (32)
- # crypto (20)
- # cursive (34)
- # datomic (45)
- # emacs (3)
- # events (1)
- # figwheel (1)
- # figwheel-main (10)
- # fulcro (30)
- # graphql (14)
- # hoplon (12)
- # hyperfiddle (21)
- # jobs (11)
- # kaocha (7)
- # klipse (8)
- # leiningen (10)
- # luminus (3)
- # nrepl (18)
- # off-topic (232)
- # onyx (8)
- # pathom (6)
- # re-frame (30)
- # reagent (3)
- # reitit (6)
- # remote-jobs (3)
- # ring-swagger (4)
- # shadow-cljs (21)
- # spacemacs (5)
- # sql (18)
- # tools-deps (23)
- # yada (2)
Ultimately my solution was to exclude the dependencies and vendor the React extern file from CLJSJS. It works, but it'd be nicer if it'd just work. 😐
Is there a cider/figwheel-main hello-world project somewhere, both for project.clj and for deps.edn? I managed fine with lein-figwheel, but I can't manage to configure using figwheel-main. i am sure I have some dependency wrong or some version incompatibility...
I have a project using it which is not really hello world
thanks @U0524T275 ! I will look at this this afternoon.
we are using figwheel-main also to build the prod js file
we have quite a few compilation to fix, but once I fixed them I would like to enforce a 0 warnings policy
is there a faster way to simply get the warnings (not sure maybe just compile all the files without producing the final js)?
and any suggestions about how to check that there were no warnings raised?