This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-15
Channels
- # aleph (24)
- # announcements (8)
- # babashka (27)
- # beginners (55)
- # biff (4)
- # calva (32)
- # cider (5)
- # clj-kondo (11)
- # clojure (59)
- # clojure-android (3)
- # clojure-australia (1)
- # clojure-belgium (6)
- # clojure-dev (21)
- # clojure-europe (26)
- # clojure-nl (1)
- # clojure-norway (17)
- # clojurescript (19)
- # css (1)
- # data-science (10)
- # datahike (17)
- # events (3)
- # figwheel-main (4)
- # honeysql (1)
- # hugsql (5)
- # hyperfiddle (1)
- # jobs (1)
- # leiningen (3)
- # lsp (6)
- # malli (5)
- # meander (4)
- # nbb (6)
- # off-topic (87)
- # pathom (19)
- # portal (2)
- # re-frame (4)
- # reitit (6)
- # releases (1)
- # remote-jobs (3)
- # shadow-cljs (29)
- # sql (8)
- # tools-deps (6)
- # xtdb (7)
Actual cider specific question: I have a deps.edn file that previously had zero dependencies. I've just added a :dev alias with a single item extra-paths vector to ["src/dev"]. I've also added an :extra-deps key with a library. When I try to evaluate a namespace form that uses this dependency I understandably find that this thing isn't found on the classpath. I know dependencies are injected on cider-jack-in - but I've already previously done that. What is the shortest path to getting this new dependency on my classpath so I can use it in this src/dev/blah.clj file?
I was able to do this with C-u C-u M-x cider-jack-in
then adding :dev
to the existing server commadn
Cider is great because it does a lot of automatic stuff for us, and sometimes i forget where and what Cider does. I believe the extra paths will only stick if you cider-jack-in
using argument -A:dev
Another way to confirm is instead to manually start clojure from the command line, clj -A:dev
then do a cider-connect
. Once your up and running in a Cider session you can try to diagnose your classpath by doing M-x
cider-classpath
Hope this helps...