Yep. Other than reverting this change locally there's nothing else you can do.

The change was made so that CIDER would consider every possible nREPL that's running for a particular project, which is the better behavior IMO.

@U051BLM8F I think it would make more sense if metadata about where the port came from was maintained, because a list of a large integers isn't really useful as an enduser if I can't distinguish which one belongs to which sort of process. Or maybe some kind of preference mechanism could exist?

I'm always open to ideas for improvements, so feel free to file a ticket about this. I agree that pairing the port number with the file it came from makes sense.

Ok, thank you - I will see if I can file a ticket!

Ok, ticket filed.

it’s totally unclear to me what is going wrong locally, and unfortunately nothing on the page, paired with that generic message, is illuminating.

sending full error message…

[nREPL] Starting server via /opt/homebrew/bin/clojure -Sdeps '{:deps {nrepl/nrepl {:mvn/version "0.9.0"} cider/cider-nrepl {:mvn/version "0.28.4"} cider/piggieback {:mvn/version "0.5.2"}} :aliases {:cider/nrepl {:main-opts ["-m" "nrepl.cmdline" "--middleware" "[cider.nrepl/cider-middleware,cider.piggieback/wrap-cljs-repl]"]}}}' -M:test:dev/repl:cider/nrepl
[nREPL] server started on 52185
[nREPL] Establishing direct connection to localhost:52185 ...
[nREPL] Direct connection to localhost:52185 established
error in process filter: user-error: ClojureScript is not available.  See  for details
error in process filter: ClojureScript is not available.  See  for details

after running cider-jack-in-cljs and selecting node

node is present

is this a shadow project or figwheel or bare cljs?

bare cljs, but shadow fails as well

shadow starts but then that same error comes up

npx shadow-cljs node-repl

ignore shadow for a second then. do you have clojurescript on your classpath?

do you mean clj, clojure?

is there a cljs binary?

no i mean clojurescript on your classpath

I didn’t even know that that was a thing!

https://clojurescript.org/guides/quick-start

no mention of a standalone cljs command anywhere here and I’ve never done that. that would be an obvious issue then since I don’t have it 🙂

this puts clojurescript on your classpath

i am not talking about a standalone cljs command. I’m talking about the clojurescript jar present on your classpath

can you give me a way to see what the classpath is, in the context of the command that cider-jack-in-cljs is running?

ah

sorry, missed your image

okay that’s closer. I have (cider-clojure-cli-aliases . ":test:dev/repl") in dir locals;

but the cljs dep is under a different alias

sounds like I need to get the cljs alias in there too

then the error message that it cannot find clojurescript seems very apt

yeah. you are asking it to start up a clojurescript repl but it cannot possibly do so

yes, but think of the debug steps: • that image is saying to put the clojurescript dep at the top level of deps.edn, which is poor form for any library; • realistically it’s always in an alias, which you can tune with an emacs variable documented somewhere else • that alias is set in a .dir-locals.el file, and named cider-clojure-cli-aliases, which you might imagine is separate from some cljs variable • that all requires some knowledge of how deps.edn aliases are layered, which is fine;

“:yeah. you are asking it to start up a clojurescript repl but it cannot possibly do so” this was clear from the behavior 🙂

I appreciate the help, just pushing back on the hint, maybe misperceived, that the deduction chain here was super obvious

That image is from the document you linked me. I pointed to the step I was talking about

a better error might say “the clojurescript jar is missing from the classpath. you’re currently using deps.edn with the following aliases configured: <blah blah>. make sure that an entry like [clojurescript “blah”] is present in the :deps` value for one of those aliases.”

That’s an excellent suggestion. If you made an issue I suspect there would be some interest

> “then the error message that it cannot find clojurescript seems very apt” it was apt! just not as helpful as you were!

Sorry. I’ve seen this error pop up when things will actually work out. So part of my diagnosis is finding out if this is correctly erroring and it cannot work, or if it is erroring but it would have worked if we weren’t trying to be clever

sure, that makes sense. definitely not an easy problem, with so many editors, build setups etc

found an old issue about it: https://github.com/clojure-emacs/cider/issues/2230

Never mind, I restarted Emacs and I don't see the error anymore