Can I connect to shadow-cljs's nREPL with my own code? Since my code is in ClojureScript, while nREPL was built in Java.

I found socket REPL is much easier, guessing it's not in shadow-cljs...

of course socket repl is in shadow-cljs

oh... just not found in docs

in the target/shadow-cljs folder there is a socket-repl.port file

thats the port of the socket repl

also the is a cli-repl.port file

also a socket REPL but it does NOT print a prompt

otherwise its the same

sounds good

cli-port is used by the shadow-cljs script itself to communicate with the server

I hate that prompt, hard to building tools

how are the ports picked? randomly

?

yes

:socket-repl {:port 123} can be configured

cli-repl is always random

cool

well..

guess I would like to try cli-repl...

anyone used it in building tools before?

no idea

bear in mind that the cli-repl is meant for internal use and not officially part of the public API

I don't plan on removing it but its also not super well suited for tooling

the shadow-cljs script is simple since it just sends one thing

https://github.com/thheller/shadow-cljs/blob/master/src/main/shadow/cljs/npm/client.cljs#L56

after that it just reads

nrepl is used by pretty much all tools

maybe prepl in the future? don't know what that is about yet

actually that's what I need to build a tool...

socket REPL is nice, but I don't know how to deal with the prompts

maybe trying regular expression... could be tedious.

socket REPL isn't really meant for tools

so nREPL?

nrepl is what all other tools use yes

you can in theory use the cli-repl thing but that is literally just socket repl without prompt

stilll has issues as soon as anything prints to stdout

I was suggested node-nrepl-client last night, tried and it worked, but the message it returned is hard to understand

nrepl is weird yes

nrepl ╮(￣▽￣")╭

prepl is coming https://github.com/clojure/clojure/commit/86a158d0e0718f5c93f9f2bb71e26bc794e7d58e

that solves some of the issues but nowhere near what nrepl provides

what are you trying to build?

I want to send a piece of Clojure code from my own process, and eval it in the runtime(browser, I mean), what's your suggestion?

"prepl" is so new, no Google results

yeah .. no one knows what that is about yet. it was commited by Rich 2 days ago ...

I can see what it does by reading the code ... I don't know WHY though

so sending things to the browser is complicated

shadow-cljs is already doing that...

in cljs-repl.

yes. but you need a running watch for that and a connected client

I just noticed after using my own editor for so long, I don't even use some basic tool others are using in tools like EMACS.

...trying to script my own version

my tool will base on that, page connected to shadow-cljs.

well if you don't care about the result at all you could just run shadow-cljs cljs-repl your-build and print all stdout somewhere

but parsing the output is painful

but you don't have to parse the output

only thing I can do at current is generate Clojure code, send it somewhere, maybe print the logs also.

output in browser, or in my process, I don't mind.

what the shadow-cljs script does is connect to the cli-repl port

send (shadow.cljs.devtools.cli/from-remote "some-uuid" "another-uuid" ["cljs-repl" "your-build"])

after that the output is just printed

all input is sent to the socket as-is

so the cljs-repl command will read and process it

tried in my nodejs REPL, doesn't know how it works..

where should I get the uuids,

and where to put my code?

look at this file https://github.com/thheller/shadow-cljs/blob/master/src/main/shadow/cljs/npm/client.cljs

there are no docs for this and there probably won't be

haha..

but it is very simple code

ALL tools use nrepl. there is a reason for that.

unrepl is newer but not many tools use it (yet). prepl will be something official but nobody knows when this will get adoption. socket-repl still isn't used by anything and thats has been there since 1.7.

strange situation...

not really, just use nrepl

what does this argument do? ["cljs-repl" "your-build"]

just follow the code

these are all internal details that are not part of the public API

and never will be

if you give me a clear definition of what you want to do I can take a look at implementing something to make that work

（＞﹏＜）

still trying...

but all this is internal stuff I needed.

just saying that you could use it to make something semi reliable

but it has lots of issues and nrepl is far more reliable and tested

I just saw people evaluating code from their editors last night.

also already has reliable middleware configuration and that stuff

yes, everyone does that via nrepl

cursive doesn't even support connecting to remote socket REPLs (yet)

so people don't do that in Cursive?

I do it pretty much always via nrepl

turned out nrepl is the thing I have to code anyway.

I would recommend using that yes

socket repl or even the cli-repl gets destroyed by any print you don't expect

if you attempt to parse the output at all

works fine if you never try to parse the output though

and you don't have to parse the output strictly speaking

no, I don't parse the output

but yeah REPL in my editor is a must have for Clojure. not so much for CLJS though.

then the prompt should not be an issue?

I'm still thinking about if there any way to improve my workflow. I'm the only user, and no one would write plugins for me except myself.

A cursive user told me they were switching to https://github.com/pedestal/pedestal/blob/master/service-tools/src/io/pedestal/service_tools/dev.clj#L23 recently

(Live-reload for clojure)

yeah prompt is not a issue for me.

@dominicm I toyed with that idea once but it is horrible in practice 😛

but cursive has a button for this so I guess the only difference is that I can trigger it when I want to

The cursive user told me they utilized the auto-save on un-focus feature, which surprised me 😂

it is strange though. for clojure I definitely prefer manually requiring/reloading namespaces and doing things via the REPL

in CLJS I just let live-reload do its thing and almost never use the REPL

strange how the workflows can be so different

took me long while to realize ["cljs-repl" "browser"] does nothing but connect me to the REPL in browser..

do people who eval code form EMACS or other editors call this API too?

no one uses this API. no one even knows about this API.

everyone uses nREPL.

but... when they use nREPL, the code is evaluated in your Clojure process, not in the browser?

https://shadow-cljs.github.io/docs/UsersGuide.html#_nrepl_usage

so.... just used it to start watching...?

I can't answer that. YOU need to decide what you want to do.

you can start the watch yes, you can also assume it is running already

Umm...

I don't know what your tool needs

I want to click an expression in my editor, and it's evaluated in browser.

also pressing keyboard shortcut probably

after pressed, my editor will generate code and send to shadow-cljs

and let shadow-cljs send that piece of code into the connected browser tab, and eval.

just like people did to eval selected code in a Clojure REPL with nREPL,

difference is my runtime is the browser, too far to send the code.

I think I have got all the code needed to make it happen now..

Thanks for the help. Going out for some hours. I will try add it in my editor later, and gather feedbacks.

Hi, I have the problem that *target* is set to default instead of nodejs (what I would expect) when the build is configured with :target :node-script. Can anyone give me a hind here where I am running into?

hmm what is *target*?

hehe cljs.core/*target* I presume. Didn't even know that existed

Yes exactly, before this me neither 😉

You can set :compiler-options {:closure-defines {cljs.core/*target* "nodejs"}} in your build

seems to be a self host thing though?

ah hmm no its used in some places

I can set it to nodejs for :node-script and :node-library builds

Gosh, thanks, I already tried various combinations to get this set via clojure-defines. Now it works.

I think that would be the correct solution.

I've opened an issue: https://github.com/thheller/shadow-cljs/issues/198

hehe opened while I was writing the commit message. insta-closed 😉

Thanks a lot! 👍

by the way @thheller, just to follow up on my sorrows of the past few days: not only was I battling the weird stale state issue, but it turns out that due to a known bug in an old version of nodemon (!!!), my server was restarting without me noticing every time I saved my client code in atom (actually it would restart even when i switched tabs). so the hot code reloading was appearing to break in the most nondeterministic and impossible to debug ways imaginable. talk about bad luck.

doh!