This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-19
Channels
- # adventofcode (18)
- # announcements (1)
- # babashka (153)
- # beginners (73)
- # bristol-clojurians (4)
- # calva (1)
- # cider (6)
- # clj-kondo (38)
- # clojure (154)
- # clojure-dev (12)
- # clojure-europe (7)
- # clojure-finland (11)
- # clojure-nl (70)
- # clojure-spec (13)
- # clojure-uk (101)
- # clojuredesign-podcast (2)
- # clojurescript (15)
- # core-async (30)
- # cryogen (1)
- # cursive (5)
- # devops (1)
- # duct (4)
- # figwheel-main (1)
- # fulcro (19)
- # jobs (12)
- # kaocha (17)
- # luminus (2)
- # malli (8)
- # music (5)
- # nrepl (13)
- # off-topic (20)
- # overtone (3)
- # re-frame (7)
- # reagent (38)
- # shadow-cljs (13)
- # specter (3)
- # tools-deps (6)
- # vim (7)
Hey folks I've been using figwheel-main with the default template for a while: https://github.com/bhauman/figwheel-main-template but now I just found a problem. I'd like to specify {:closure-defines {goog.DEBUG false}}
for my prod build but the templates only has one dev build. If I add a prod.cljs.edn
configuration then the index.html will get confused because it stills tries to load the dev.cljs.edn
configuration. The way the template does it is to supply a -O advanced
before compiling the dev build. But there seems to be no way to specify a closure-define
before building the dev config. I find it hard to use the template since it doesn't clearly separate dev, test and prod, and reading the documentation for the command flags is a struggle too. There are not many examples of people using fighweel-main
and the few that exist https://github.com/pesterhazy/cljs-spa-example have an entire folder full of scripts that copy around the index.html files which to me defeat the purpose of having a build tool. Can anyone help a brother out please? 🙂