This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-03-27
Channels
- # aleph (5)
- # announcements (18)
- # beginners (200)
- # cider (25)
- # cljdoc (4)
- # cljsrn (3)
- # clojure (90)
- # clojure-europe (3)
- # clojure-finland (5)
- # clojure-france (1)
- # clojure-houston (1)
- # clojure-italy (8)
- # clojure-nl (15)
- # clojure-spec (24)
- # clojure-uk (20)
- # clojurescript (199)
- # core-async (2)
- # cursive (45)
- # data-science (14)
- # datomic (33)
- # duct (13)
- # fulcro (4)
- # graphql (3)
- # kaocha (9)
- # leiningen (24)
- # nrepl (16)
- # off-topic (105)
- # pathom (15)
- # pedestal (28)
- # re-frame (1)
- # reagent (14)
- # shadow-cljs (28)
- # spacemacs (8)
- # tools-deps (8)
- # vim (4)
@cfleming That’s the first time I see such an error. That new var is simply a way for tools like Lein to print properly the nREPL url now that it has more transports (before all tools had hardcoded nrepl://
). The var was actually added in nREPL 0.5.
What’s his piggieback version? Your user should be on 0.4 for things to work properly.
@bozhidar Actually, it’s not the first time you’ve seen it :-): https://github.com/eraserhd/rep/issues/1
> https://github.com/eraserhd/rep/issues/1 It’s different here - he injected an older version of nREPL when Lein expected a newer one. I think you mentioned your user was on 0.6, that’s why I can imagine how this can be missing.
Yeah, I don’t know much about his setup - he just said it’s a CLJS project and he gets the error at startup. But I think the fact that Cursive has upgraded the nREPL it uses is misleading, since if he’s using lein that version won’t be used anyway, it’ll be whatever lein is using.
I suspect that upgrading Cursive will have caused him to use a later leiningen, which is incompatible with whatever piggieback he’s using, but I’m not sure yet.
How does Cursive start nREPL itself, btw? It doesn’t use any build tool and sorts out the projects deps itself?
That’s used when someone wants a REPL in a project that’s not managed by something like lein that will start a REPL for you. So things like Gradle or Maven, or a manually configured project. Then, right, Cursive will use the IntelliJ classpath and just add nREPL to it, and then inject an init script which starts the server.