This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-08-04
Channels
- # announcements (7)
- # babashka (32)
- # beginners (106)
- # bristol-clojurians (10)
- # cider (6)
- # clj-kondo (5)
- # cljdoc (10)
- # clojure (110)
- # clojure-australia (10)
- # clojure-dev (6)
- # clojure-europe (12)
- # clojure-nl (2)
- # clojure-norway (16)
- # clojure-spec (9)
- # clojure-uk (59)
- # clojurescript (105)
- # community-development (2)
- # conjure (46)
- # cursive (12)
- # data-science (1)
- # datalog (26)
- # datomic (37)
- # docker (4)
- # emacs (10)
- # events (1)
- # fulcro (8)
- # graalvm (2)
- # jobs (1)
- # jobs-discuss (1)
- # malli (24)
- # meander (13)
- # off-topic (52)
- # pathom (4)
- # polylith (17)
- # proletarian (4)
- # react (1)
- # rewrite-clj (4)
- # shadow-cljs (56)
- # sql (21)
- # xtdb (14)
@vemv The docs say it's a library as well. How would it be used with tools/deps (without Leiningen)?
I have an issue open for that It's doable, I have a plan. I should just get to it some weekend. Feel free to nudge me over the issue tracker if too much time passes
btw PR welcome if anyone wants a deps.edn adventure... it's kind of low-hanging fruit I actually use deps.edn frequently / at work. My workaround is slurping deps.edn from Leiningen. I like all my tooling lein-based even when using deps.edn
I'm curious to know how you do that. I've always used Leiningen, but my new job uses deps.edn. I haven't dug into the interop. Once I got CIDER working with front and back end, I moved on....
I use this generic project.clj that will work with most deps.edn files out there. There can always be edge cases though :)
https://gist.github.com/vemv/7239033e8a16f2cc24b32f637bf42959
This approach is superior to the plugins you can find out there IMO. If something goes wrong you can add a println
and fix it immediately
I have a bash wrapper for lein
that will copy this file to $PWD if no project.clj was found
Pretty slick! I'll have to try it out....