This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-05-30
Channels
- # announcements (9)
- # babashka (22)
- # beginners (25)
- # calva (2)
- # cider (9)
- # clj-on-windows (15)
- # clj-otel (29)
- # clojure (73)
- # clojure-conj (4)
- # clojure-europe (69)
- # clojure-gamedev (4)
- # clojure-nl (1)
- # clojure-norway (19)
- # clojure-sweden (12)
- # clojure-uk (4)
- # clojuredesign-podcast (6)
- # clojurescript (5)
- # clr (52)
- # community-development (2)
- # cursive (5)
- # datahike (3)
- # datalevin (5)
- # datascript (4)
- # datomic (14)
- # dev-tooling (13)
- # events (4)
- # gratitude (12)
- # honeysql (1)
- # hyperfiddle (15)
- # jobs (1)
- # lsp (19)
- # malli (8)
- # meander (2)
- # missionary (10)
- # off-topic (12)
- # polylith (3)
- # reagent (8)
- # reitit (2)
- # remote-jobs (1)
- # shadow-cljs (31)
- # timbre (4)
Babashka on master now can run https://github.com/cognitect-labs/transcriptor/blob/master/transcriptor.clj, a REPL-based testing library, thanks to @highpressurecarsalesm! Bob has been making great contributions to babashka so thanks a lot!
I'm interested in using https://github.com/clj-commons/pomegranate/ in babashka. it relies on a lot of interop, mostly focused in org.eclipse.aether
. To double check, that's just a no-go, right?
correct. perhaps this is an a x-y problem though, what do you want to do with pomegranate in bb?
i'm looking to use slipset's deps-deploy to deploy to clojars from babashka
i'm building a lein
-like cli tool that automates some common tasks i have in my projects as all of my build.clj's look exactly the same (minus the :lib
differences lol), and with tools.bbuild i'm able automate compilation/jar/uberjar building
i'd like to implement deploying as well, and deps-deploy is the easiest method for it that i've found (all other libraries seem to rely on it (liquidz/build.edn, depstar, etc)
deps-deploy is a thin wrapper over pomegrante:
(defmethod deploy* :local [{:keys [artifact-map coordinates]}]
(println "Installing" (artifact coordinates) "to your local `.m2`")
(aether/install :artifact-map artifact-map
:transfer-listener :stdout
:coordinates (mvn-coordinates coordinates))
(println "done."))
where aether
is cemerick.pomegranate.aether
perhaps in this case it's better to just call out to JVM Clojure (you can construct clojure CLI calls with (babashka.clojure "-Sdeps" etc)
then.
ah yeah, that could work
thanks, i'll give that a try
Is there a mechanism in babashka.process
that would allow me to wait and add input after some amount of time (preferably determined by the command itself)?
My use case is that a lot of folks I know write âscriptsâ that are interactive via a JS library called prompts
and I need to run it a lot of times with predetermined input, so I figured scripting babashka to do it for me was a good option.
I kinda figured, just wanted to check đ
Would I just loop/wait and check :out
?
You didnât specify this but do you want to write after waiting for some time or after some output appeared?
I need to write after some output appears. For some reason, we have a bunch of scripts that donât take inputs via the CLI and are interactive only