This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-14
Channels
- # announcements (7)
- # aws (1)
- # babashka (1)
- # beginners (19)
- # calva (9)
- # clj-commons (4)
- # clj-kondo (64)
- # clj-on-windows (27)
- # cljsrn (12)
- # clojure (127)
- # clojure-bay-area (3)
- # clojure-europe (25)
- # clojure-hungary (7)
- # clojure-nl (1)
- # clojure-norway (9)
- # clojure-spec (5)
- # clojure-survey (2)
- # clojure-uk (22)
- # community-development (5)
- # core-async (19)
- # cursive (29)
- # datascript (8)
- # events (1)
- # fulcro (2)
- # graalvm (3)
- # jobs (1)
- # lsp (155)
- # malli (18)
- # nbb (6)
- # off-topic (86)
- # pathom (2)
- # rdf (18)
- # re-frame (9)
- # releases (2)
- # scittle (24)
- # shadow-cljs (33)
- # xtdb (4)
Now that lein2deps is a thing: https://clojurians.slack.com/archives/C06MAR553/p1665746587901169
Perhaps we could add a deps.edn
generated by that thing to clj-commons/hickory so people can at least start using it as a git dep :)
In Aleph we have a step in the CI build job which ensures that project.clj
and deps.edn
are in sync. Feel free to steal 🙂
See https://github.com/clj-commons/aleph/pull/625 for the initial work and https://github.com/clj-commons/aleph/pull/635 for the switch to lein2deps
.
In Aleph we have a step in the CI build job which ensures that project.clj
and deps.edn
are in sync. Feel free to steal 🙂
See https://github.com/clj-commons/aleph/pull/625 for the initial work and https://github.com/clj-commons/aleph/pull/635 for the switch to lein2deps
.