This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-12
Channels
- # aleph (3)
- # announcements (15)
- # architecture (6)
- # babashka (35)
- # babashka-sci-dev (10)
- # biff (5)
- # calva (9)
- # cherry (1)
- # cider (44)
- # clj-kondo (31)
- # cljfx (1)
- # clojure (108)
- # clojure-europe (32)
- # clojure-norway (12)
- # clojurescript (15)
- # conjure (3)
- # cursive (8)
- # datahike (1)
- # datalevin (19)
- # datascript (1)
- # datomic (59)
- # emacs (4)
- # graphql (3)
- # jobs (1)
- # luminus (6)
- # meander (9)
- # membrane (45)
- # nbb (67)
- # off-topic (16)
- # portal (3)
- # remote-jobs (1)
- # scittle (8)
- # shadow-cljs (46)
- # test-check (7)
- # tools-deps (5)
- # vim (63)
- # web-security (11)
- # xtdb (15)
I found it slightly surprising that the docs for neil dep add
hints to the user to run neil add dep --help
for more info, switching the argument order around.
$ neil -h
...
dep
add: Adds --lib, a fully qualified symbol, to deps.edn :deps.
Run neil add dep --help to see all options.
...
Idea: neil dep upgrade
.
neil dep upgrade
- lists upgradeable deps
neil dep upgrade :lib LIB
- upgrade specific lib to latest
neil dep upgrade :everything
- upgrade all upgradeable libs.
Potential problems:
⢠projects can have dependencies in project.clj, deps.edn or bb.edn.
About language: This would really be a "batch control dependency version". Which is sort of what neil dep add
is too.
So ... perhaps we could just generate input for neil dep add
? In which case it might make sense for neil dep add
to support adding multiple libraries in a single CLI command.