-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting stuck on "adding middlewares" #43
Comments
Please make sure you are using |
Ah, I have no idea which REPL is included in Shadow-CLJS. It might be an old one, I guess. Edit: it seems that Shadow-CLJS is using |
I have never tested with CLJS. There are a few middlewares which are clojure-native, not sure how it goes with CLJS REPL. If you can figure out what’s going on and what’s needed to make CLJS tick, it would be a great help. See also #31 |
Shadow-CLJS exposes a normal CLJ socket REPL as well as an NREPL, so I'm not connecting to CLJS. I've never bothered running a socket or NREPL separately, seeing as Shadow provides one: https://shadow-cljs.github.io/docs/UsersGuide.html#_clojure_repl Once connected to the CLJ REPL, it's possible to tunnel into the CLJS one. |
I'm also suffering from the same issue |
TL;DR shadow-cljs implements nrepl protocol for v0.4. Clojure Sublimed expects at least 0.8. I encountered the same issue. After I turned the A few hours later, I found out that shadow-cljs redefines middlewares for nrepl and requires them one by one here I will post an update if I resolve this, but I wanted to share my findings anyway to save time for the next person trying to figure it out. |
Thanks @alekzvik! Another angle of attack might be for Clojure Sublimed to not require extra middlewares for CLJS |
@tonsky, or they can be optional. A describe op can return a list of supported operations from the nREPL server. |
Should work in 2.8.0 via Connect shadow-cljs command |
I'm attempting to connect to a server hosted by Shadow-CLJS:
There are no error messages in the log, as I can see.
The text was updated successfully, but these errors were encountered: