This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-02-15
Channels
- # announcements (27)
- # architecture (15)
- # aws (2)
- # babashka (5)
- # beginners (77)
- # calva (42)
- # cider (22)
- # clj-kondo (47)
- # cljfx (7)
- # clojure (66)
- # clojure-australia (1)
- # clojure-europe (32)
- # clojure-france (10)
- # clojure-israel (2)
- # clojure-italy (1)
- # clojure-nl (8)
- # clojure-uk (53)
- # clojurescript (29)
- # conjure (28)
- # core-async (2)
- # cursive (26)
- # data-science (1)
- # datascript (11)
- # datomic (33)
- # emacs (4)
- # fulcro (5)
- # girouette (3)
- # helix (1)
- # jobs (2)
- # leiningen (17)
- # luminus (2)
- # malli (15)
- # music (2)
- # off-topic (51)
- # pathom (3)
- # rdf (91)
- # remote-jobs (1)
- # reveal (7)
- # sci (6)
- # shadow-cljs (10)
- # spacemacs (3)
- # sql (23)
- # tools-deps (52)
- # uncomplicate (2)
- # vim (3)
- # xtdb (9)
We are now using babashka to solve the deps.edn mono-repo problem. We generate deps.edn for all sub-projects using a script which pulls default versions from a common deps.edn file. https://gist.github.com/borkdude/58f099b2694d206e6eec18daedc5077b
Same here! Although I'm generating a custom deps.edn per sub-project from a single edn config file at the root of the monorepo. Merging a sub-project specific template is an interesting twist which may be useful for isolating some very specific configs/aliases. OTOH, it's also nice to have everything visible and easily comparable in one edn config.
Nice!
A babashka script to find var usages in the current project (using clj-kondo pod): https://gist.github.com/borkdude/841d85d5ad04c517337166b3928697bd