it seems like most of the issues mentioned in https://groups.google.com/d/msg/cursive/ntvsiLAehY0/BZ5bLkUwEwAJ are now fixed in 2019.2.1 (build 192.6262.58). however, https://youtrack.jetbrains.com/issue/IDEA-211736 (Fixed in builds: 192.6455) didn’t seem to make the cut.

I'll give it a week or so

I’ve updated over on the mailing list thread: https://groups.google.com/d/msg/cursive/ntvsiLAehY0/6LkDZSdyAAAJ

ah, found it here: https://github.com/thheller/shadow-cljs/wiki/Cursive looks like i'll stick to emacs/cider for the front-end stuff.. 🙂

this isn’t really documented cohesively anywhere as far as I remember, but here’s how I do it: 1) create an nrepl and set it to connect to the .nrepl-port created by shadow by choosing “Use Leiningen REPL port” 2) go to Tools > REPL > Add New REPL Command 3) Select Execute Command and put in (shadow/repl :my-build-id) replaced with the correct build id, obvs 4) start your repl, then navigate again to Tools > REPL > Commands and select your new command

the ns to start your shadow repl in cursive is a little different depending on what version you’re on. I’m on 2.8.40

if you’re worried about the deps resolving within cursive, I’d recommend using deps.edn and letting shadow integrate with that. at least that’s what’s working for me 🤷

FWIW the work I’m doing on migrating Deps right now will also make native support for Shadow easier.

@U0567Q30W glad to hear, keep up the good work! 🙂