Frequently Asked Questions

Is cider-nrepl specific to CIDER?

No, the name is a bit of a misnomer. All of the functionality in cider-nrepl can be leveraged by any nREPL client. Many Clojure editors are built on top of cider-nrepl.

If we were naming the project today we would have gone with orchard-nrepl. Naming is hard!

Does cider-nrepl support ClojureScript?

Yes, it does. The support, however, is partial and not all of the functionality is available for ClojureScript. Ops that only make sense on the JVM reply with a clojure-only status when invoked in a ClojureScript session.

Does cider-nrepl support ClojureCLR?

No, it does not. There are two reasons for this:

  • The lack of a compatible nREPL implementation for .NET

  • The usage of Java APIs in the current implementation of cider-nrepl

Both problems are solvable, but they will require significant amount of work and knowledge of .NET that the current cider-nrepl team does not have.

Are there any other nREPL middleware libraries similar to cider-nrepl?

Yeah, there are. Most notably there’s refactor-nrepl which provides a lot of refactoring functionality for Clojure editors.