First, thank you so much for Fireplace and your years of work on Vim plugins! :pray:
There are now runtime environments that are pure ClojureScript running on e.g. Node and they have no Clojure/JVM or Piggieback in sight. For example nbb is cljs on Node and provides a basic nREPL (there are others). Some other nREPL clients are able to connect to and use this as documented in that link. Not all features are supported but you can at least send code and have it run.
To stand up an nbb nREPL:
mkdir nbb-nrepl-test; cd nbb-nrepl-test
echo {} > package.json
npm i nbb
npx nbb nrepl-server :port 1337
In Fireplace after running gvim test.cljs I can connect to this with :Connect 127.0.0.1:1337 and I can do :CljEval and it works, as I guess Fireplace assumes it's a regular Clojure nREPL. However when I do cqq on a form I get:
Fireplace: no default ClojureScript REPL
Is there a way for me to tell Fireplace that the current REPL connection it has open is already a ClojureScript REPL? If not, any tips or pointers for adding thise so I can raise a PR are much appreciated! Many thanks!
First, thank you so much for Fireplace and your years of work on Vim plugins! :pray:
There are now runtime environments that are pure ClojureScript running on e.g. Node and they have no Clojure/JVM or Piggieback in sight. For example nbb is cljs on Node and provides a basic nREPL (there are others). Some other nREPL clients are able to connect to and use this as documented in that link. Not all features are supported but you can at least send code and have it run.
To stand up an
nbbnREPL:In Fireplace after running
gvim test.cljsI can connect to this with:Connect 127.0.0.1:1337and I can do:CljEvaland it works, as I guess Fireplace assumes it's a regular Clojure nREPL. However when I docqqon a form I get:Is there a way for me to tell Fireplace that the current REPL connection it has open is already a ClojureScript REPL? If not, any tips or pointers for adding thise so I can raise a PR are much appreciated! Many thanks!
Updated to add: here is a thread where they work out the same issue in CIDER on Emacs: https://github.com/clojure-emacs/cider/issues/3061