This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-20
Channels
- # announcements (16)
- # babashka (104)
- # beginners (77)
- # bristol-clojurians (1)
- # calva (3)
- # chlorine-clover (50)
- # cider (19)
- # clojure (73)
- # clojure-australia (1)
- # clojure-europe (37)
- # clojure-france (3)
- # clojure-nl (3)
- # clojure-norway (13)
- # clojure-spec (21)
- # clojure-uk (79)
- # clojurescript (225)
- # conjure (102)
- # cursive (11)
- # datascript (1)
- # datomic (1)
- # defnpodcast (1)
- # events (3)
- # figwheel-main (2)
- # fulcro (49)
- # ghostwheel (10)
- # helix (1)
- # kaocha (17)
- # leiningen (10)
- # meander (1)
- # off-topic (26)
- # other-lisps (3)
- # pathom (5)
- # re-frame (40)
- # reagent (6)
- # reitit (33)
- # shadow-cljs (107)
- # testing (3)
- # tools-deps (68)
- # xtdb (16)
- # yada (3)
Is there a way to run lein repl
and pass to it a form to evaluate without leaving the repl?
@viebel https://github.com/technomancy/leiningen/blob/stable/sample.project.clj#L373-L376
i'm trying to debug an auth issue when downloading dependencies. when i run 'lein deps :tree' to see exactly where the offending dependency is coming from though, i get the unauthorized error before the tree prints out at all
is there a way to see what the dependency tree was up to the point where the offending dep derailed things?
@nickmbailey you can try DEBUG=true lein deps :tree
but not sure it’ll be enough
yeah actually the stack trace that prints out when you add DEBUG=true shows the direct parent of the dep that failed to resolve
thanks @mikerod!