This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-12
Channels
- # announcements (13)
- # aws (18)
- # babashka (60)
- # babashka-sci-dev (83)
- # beginners (32)
- # biff (18)
- # calva (22)
- # cider (8)
- # clj-on-windows (101)
- # clojure (59)
- # clojure-bay-area (2)
- # clojure-europe (36)
- # clojure-india (4)
- # clojure-nl (3)
- # clojure-norway (5)
- # clojure-spec (4)
- # clojure-uk (1)
- # clojurescript (5)
- # conjure (1)
- # core-async (10)
- # cursive (7)
- # data-science (5)
- # datahike (10)
- # datalog (11)
- # datomic (3)
- # docker (3)
- # figwheel-main (2)
- # gratitude (3)
- # improve-getting-started (1)
- # introduce-yourself (5)
- # jobs (3)
- # joyride (12)
- # leiningen (1)
- # lsp (67)
- # malli (27)
- # off-topic (36)
- # random (1)
- # rdf (1)
- # re-frame (17)
- # reagent (21)
- # reitit (4)
- # releases (4)
- # remote-jobs (2)
- # ring (2)
- # sci (35)
- # shadow-cljs (28)
- # sql (3)
- # squint (9)
- # tools-deps (11)
Is there a way to automatically programatically add exclusions to deps.edn at the root level? If not, is there a reason why that would be hard to do? Or is there something else i should consider?
I know i can get a tree of deps using clj -Stree, it would seem simple enough to find the dep i wanted to exclude and walk up the tree and add it to the parent.
If you want programmatic I would use tools.deps rather than the cli
But it is somewhat tricky in that it’s not really a tree but a graph, and a dep can appear at many points
It seems :deps/prep-lib
only "activates" if you use the project as a dependency, vs. when you start the project locally. Is that intentional?
borkdude@m1 /tmp/proj $ clj -Sdeps '{:deps {current/current {:local/root "."}}}'
Error building classpath. The following libs must be prepared before use: [current/current]
borkdude@m1 /tmp/proj $ clj
Clojure 1.11.0
user=>
This also didn't work:
$ clj -Sdeps '{:deps {current/current {:local/root "."}}}' -X:deps prep
Error building classpath. The following libs must be prepared before use: [current/current]
@U064X3EF3 An idea?
Yeah, have thought about that, wasn’t sure if it would be like 20 lines of commands at some point :)
I.e. in an unprepared project, run a REPL, get an error about prep and be able to run clojure -X:deps prep
That probably makes sense but I want to go back too the origins sheets to make sure I’m not forgetting something