Fork me on GitHub
#chlorine-clover
<
2021-03-15
>
adamrenklint20:03:28

Hey, I’m having an issue similar to https://github.com/mauricioszabo/atom-chlorine/issues/217. • I’m running clj -A:dev where :dev is -m shadow.cljs.devtools.cli watch app worker • I connect with Chlorine: Connect Socket Repl and can then eval code in .clj files • I run Chlorine: Connect Embedded, but nothing happens. No error message in my terminal, REPL panel, atom dev tools. • With a .cljs file open, when running Chlorine: Evaluate Block or any other eval-commands, nothing happens. No error messages, no feedback. I’m not quite sure where to look to debug this. Would be grateful for any pointers.

mauricio.szabo21:03:23

Hi there. Right, I believe I know what's happening. Do you have the browser / node / whatever JS app you're developing open? If not, then the "Connect Embedded" will not connect. I think I forgot to add some error message 😞

mauricio.szabo21:03:54

(if you toggle "Enable experimental features" on Chlorine, you'll see the error happening)

seancorfield21:03:46

@mauricio.szabo Does that mean you can evaluate Clojure into a Clojure REPL and ClojureScript into the embedded/browser/cljs REPL at the same time? (i.e., without having to switch connections)

mauricio.szabo23:03:19

Yes, exactly :)

seancorfield23:03:36

And that would work with Figwheel Main too? Or is this somehow specific to Shadow?

mauricio.szabo23:03:45

I'm looking at figwheel support now, and prepl, after a long pause because of my job, but the ideia is to make it work with figwheel-main too

mauricio.szabo23:03:08

The last time I saw figwheel-main the socket repl support required piggieback, but maybe with prepl things can be different (or at least, I'm hoping so)

seancorfield23:03:06

Well, my basic setup is a Socket REPL running in the JVM that Figwheel Main “happens to run in” and Clover can eval Clojure code into that just fine. It was the cljs side of the house I was asking about — and I wasn’t sure how Chlorine/Clover handled the “embedded” REPL