This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (69)
- # calva (25)
- # cider (12)
- # cljdoc (17)
- # cljs-dev (60)
- # clojure (67)
- # clojure-spec (2)
- # clojure-uk (17)
- # clojurescript (46)
- # cloverage (1)
- # code-reviews (6)
- # cursive (3)
- # datascript (8)
- # figwheel-main (1)
- # fulcro (13)
- # hyperfiddle (25)
- # off-topic (7)
- # re-frame (24)
- # reagent (12)
- # reitit (24)
- # ring (8)
- # spacemacs (11)
- # specter (22)
- # tools-deps (7)
- # unrepl (1)
Btw, adding nREPL 0.4.5 won’t do anything if you’re not on
lein-master or you’re not using the standalone
nREPL had a different deployment artefact prior to version 0.3, so if you’re on lein 2.8.1 you simply can’t displace
org.clojure/tools.nrepl with something that’s basically a different artifact.
You need a version of lein that’s already using
nrepl/nrepl and only then can you influence this through your project’s config.
That’s why I created https://github.com/nrepl/lein-nrepl as an interim solution until lein 2.8.2 is released and we can just require people to upgrade to it.
There are no backward incompatible changes, but there are some features that exist only in the newer versions. Not to mention a few bugfixes.
In 0.5 the gap is going to widen when nREPL introduces the new EDN transport, native support from pretty-printing, native configuration and so on.
Potentially native authorization and truncation support will also land there, but that’s TBD at this point.
Anyways, I just wanted to point out that the dependency does nothing, otherwise you’ll be good with nREPL 0.2 for a while.
I don’t plan to drop support for 0.2 from cider-nrepl and refactor-nrepl before lein 2.8.2 is released.
But that’s certainly happening as soon as it becomes feasible, as I don’t want to cart a bunch of compatibility code around for an extended period of time.
I’ll hurry with adding some kind of jack-in to Calva so that I can quickly move together with your changes.
And what’s the sitation for people using boot or deps.edn? If you know it top of mind, that is.