This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-09-22
Channels
- # babashka (106)
- # beginners (29)
- # biff (29)
- # calva (9)
- # cider (6)
- # clj-kondo (24)
- # clojure (40)
- # clojure-europe (94)
- # clojure-japan (1)
- # clojure-nl (1)
- # clojure-norway (45)
- # clojure-uk (13)
- # clojuredesign-podcast (5)
- # clojurescript (12)
- # clr (4)
- # community-development (2)
- # conjure (13)
- # cryogen (4)
- # cursive (4)
- # deps-new (1)
- # fulcro (18)
- # hugsql (2)
- # hyperfiddle (67)
- # jobs (1)
- # malli (47)
- # meander (2)
- # missionary (34)
- # off-topic (1)
- # podcasts-discuss (1)
- # polylith (24)
- # reagent (19)
- # reitit (9)
- # sci (7)
- # shadow-cljs (3)
- # testing (28)
- # tools-deps (1)
- # xtdb (9)
hi! is there a way of excluding the default cljs compiler so I can provide my own fork of it on shadow-cljs.edn? I can do it when using deps.edn, via :
:aliases {:shadow {:classpath-overrides {org.clojure/clojurescript nil}
:extra-deps {com.github.jpmonettas/clojurescript {:mvn/version "..."}}}}
and can do a similar thing on lein project.clj, but would be great to be able to do it just on shadow-cljs.edn, since it is for a dev tool I'm creating and I guess most people uses just shadow-cljs.ednthere is no option for that no. I think its reasonable to ask people to use deps.edn
. by my guess most people do anyways
oh don't know why I thought most people were doing the other way around. Do you think it is something reasonable to implement (maybe as general exclusions) or something that is probably hard because of reasons? (not asking you to implement it btw, just curious)