I recently updated my prelude packages, and now I have an issue where I can still start a shadow-cljs repl and have it autobuild. But inline evaluation tells me it needs a cljs repl and I probably need to jack-in. I've tried to cider-assoc-buffer-with-connection manually. But that doesn't change it.

@bbss See the conversation here - https://github.com/clojure-emacs/cider/pull/2316

I haven’t investigated what’s wrong with shadow-cljs exactly, but I also don’t recall any changes on our end recently that might have caused this.

@bbss yes, I am setting the repl type manually on my side now...I personally too, haven't had time to investigate more

Okay thanks! using cider-repl-set-type seems to have done the trick, I'll read up a bit more if I run into it again. I only recently started using shadow-cljs (it's great). It was working earlier, maybe I messed up an emacs setting.

More likely something is messed up with the repl type detection with shadow, but I haven’t had time to debug it, and it seems no one else had time for this as well.

well, not manually but with something like:

(defun ar-emacs-cljs-shadow-select-repl ()
  "Return the init form a running shadow-cljs REPL."
  (interactive)
  (save-some-buffers)
  (let ((build-ids (read-from-minibuffer "Shadow-cljs build: ")))
    (ar-emacs-clj--send-to-repl
     (concat "(do (require 'shadow.cljs.devtools.api) "
             (format "(shadow.cljs.devtools.api/nrepl-select %s)" build-ids)
             ")")))
  (ar-emacs-clj--set-cljs-repl-type))

(defun ar-emacs-clj--set-cljs-repl-type ()
  "Set the cider REPL type to cljs."
  (when (or (bound-and-true-p cider-mode)
        (equal major-mode 'cider-repl-mode))
   (with-current-buffer (cider-current-repl-buffer)
     (cider-repl-set-type "cljs")
     (cider-repl-return))))

to make matters more complicated it's a chrome-extensions which runs in a slightly different browser context. It's (in early) support by shadow-cljs though and worked before. I might just have messed up my emacs..

I haven’t merged the proposed workaround mostly because I’ve decided not to merge any PRs while we merge the big connection overhaul as I don’t want @vspinu to have to deal with conflicts there.

@richiardiandrea cheers, appreciated!

make sense @bozhidar, better to get that in 😉

emacs is flexible enough that I can maintain a couple of lines of elisp for now 😉

(double wink)

I should probably take some time to learn some elisp

it's as fun as writing Clojure 😄

hahah, unbelievable!

I can say, better, at times

ah really? I guess emacs gets better as you understand it better, so I can imagine.

in terms of tooling it is super smooth imho

debugging + REPL

(well, cider has the same)