This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-05
Channels
- # asami (13)
- # aws (7)
- # babashka (4)
- # beginners (16)
- # biff (7)
- # cljdoc (10)
- # clojure (32)
- # clojure-europe (27)
- # clojure-nl (14)
- # clojure-norway (7)
- # clojure-uk (3)
- # clojurescript (2)
- # conjure (2)
- # core-async (13)
- # datalevin (4)
- # datomic (3)
- # holy-lambda (7)
- # kaocha (3)
- # lsp (23)
- # off-topic (39)
- # pedestal (10)
- # portal (5)
- # practicalli (2)
- # rdf (10)
- # releases (1)
- # shadow-cljs (66)
- # tools-deps (146)
- # uncomplicate (1)
- # xtdb (10)
Apologies if this is not the right channel but is org.babashka/spec.alpha incompatible with Clojure on the JVM? I'm trying to start a Clojure CLI REPL:
clj -Sdeps '{:deps {org.babashka/spec.alpha {:git/url "" :git/sha "8df0712896f596680da7a32ae44bb000b7e45e68"}}' Error while parsing option "--config-data {:deps {org.babashka/spec.alpha {:git/url \"\" :git/sha \"8df0712896f596680da7a32ae44bb000b7e45e68\"}}": java.lang.RuntimeException: EOF while reading You forgot one closing } - and it's not recommended to use babashka spec with clojure
1Oops, sorry, you're right; I posted the wrong thing. With a correct config I'm getting a Syntax error macroexpanding clojure.core/defn before the REPL is up.
I understand that the fork is meant to be used with babashka; I'd just like to use a Clojure REPL to explore a project that is using it (blambda). For the purposes of this experiment I think replacing the fork with the vanilla spec.alpha in deps.edn would work.