piggieback
piggieback copied to clipboard
nREPL support for ClojureScript REPLs
Based on the README (https://github.com/nrepl/piggieback#usage), it seems like I need to execute `lein repl`, then: ``` (require 'cljs.repl.node) (cider.piggieback/cljs-repl (cljs.repl.node/repl-env)) ``` in order to get a cljs repl I can...
See https://github.com/lambdaisland/deja-fu#piggieback-printing A literal like `#time/time "10:11:12"` will get parsed on the Clojure side to an `UnknownTaggedLiteral`, which then gets printed again. This printing on the Clojure side will output...
I've been doing a little digging into a simple piggieback nREPL server. I've found that messages to out and err have the message ID of the call that started piggieback...
It would be great to capture and restore all the bindings but that would cause a nightmare for all the nREPL and other middleware bindings that are present. This now...
If I promote a clj session with this: ```clojure (do (require 'cljs.repl.node) (cider.piggieback/cljs-repl (cljs.repl.node/repl-env))) ``` And then `clone` that session, I get a ”dirty” session that won't allow me to...
When starting the cljs-repl of piggieback the `*cljs-compiler-env*` does not get set causing the repl to bootstrap cljs.core on every evaluation. There should be a provision for setup errors so...
(Originally proposed in #28, which couldn't be applied due to the 0.2.0 rewrite landing.) Basic outline: 1. Once in a CLJS REPL, `:cljs/pause` would be intercepted and shift the REPL...
Not sure if this is better suited for `cider`, `cider-nrepl` or here. A "Runtime" in CLJS is a JS engine that has loaded the compiled CLJS code and somehow connected...
Currently if you evaluate any ClojureScript form via piggieback the `:file` field in the message will be ignored, and "cljs-repl" will be used as a file. When defining a var,...
This is a possible fix for https://github.com/nrepl/piggieback/issues/126