This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-26
Channels
- # ai (1)
- # announcements (7)
- # babashka (2)
- # beginners (23)
- # biff (3)
- # calva (1)
- # chlorine-clover (3)
- # cider (2)
- # clj-kondo (12)
- # clojure (25)
- # clojure-brasil (4)
- # clojure-europe (33)
- # clojure-nl (1)
- # clojure-norway (7)
- # clojure-uk (1)
- # clojurescript (30)
- # clr (6)
- # consulting (1)
- # cursive (14)
- # data-science (1)
- # datalevin (4)
- # datomic (3)
- # events (4)
- # graphql (1)
- # gratitude (2)
- # hoplon (10)
- # inf-clojure (3)
- # interceptors (1)
- # introduce-yourself (1)
- # off-topic (13)
- # pathom (2)
- # pedestal (12)
- # rdf (14)
- # releases (6)
- # sci (17)
- # shadow-cljs (12)
when you set :lein true
or :deps true
in shadow cljs config, basically everything about dependency management is handed off to lein or deps.edn. so overriding dependencies depends on (1) the library youre pulling in, and (2) how you would override that with your tool
with deps.edn, I can pass multiple files, so that's how I'd solve that. I don't think shadow offers that option, hence the question
do you have a minimum example project and does it work with other tools that can use deps.edn?
i dont really know how to use deps.edn, but with leiningen you can use either :exclusions
or :managed-dependencies
to replace dependencies with exact versions specified in your project. I’m assuming deps.edn offers a similar key for these things, so I’m not sure why multiple files are needed to achieve what you want
According to https://clojure.org/reference/deps_and_cli, it looks like :override-deps
should work for what you want?
I'd like to generate overrides without having to update the base deps.edn. With plain deps, I can do it with clj -Sdeps '{ ... }'