As a side node, I think this is the only thing missing for me to make this the best ClojureScript editor experience and have more JS devs migrate I tried emacs just to get better completion but I just couldn’t get away from using cursive because it is way too good. Only after not using it, did I realize how good it actually was 😄

Not trying to drive you away from Cursive (I have been a happy and constant user since 2014) but have you had a look at VS Code + Calva? While I haven’t been doing ClojureScript for years now, for some reason I think it currently might have an edge over Cursive in modern cljs support. I’m not certain though, just asking whether you tried it.

Yes, I tried Calva + VS Code. VS Code has been my editor for 4-5 years. Couldn’t go back after switching to Cursive + IntelliJ, even for pure JS projects. Main issue (for me) is that it does not support vim which is a deal breaker for me. I think you are right, since it uses cider underneath, it should have the same functionality as Emacs. Still, I find the best experience is in Cursive and since this is important to JS devs, I figured to open the discussion

I’ve been unwilling to add support to Cursive relying on IntelliJ’s JS support, because that support would only be available on paid versions of IntelliJ. However, the sad fact is I’m not getting around to a better solution on my own because of the enormous nature of the task. So I’m reconsidering this at the moment.

I’m already on the paid version, so for me it would be perfect. Indeed, I see what you mean that even if you include it, it would be limited to paid users, which I’m not sure the % of cursive users who are. If you put a survey on wether to include intelliJ’s JS support on the paid version I would say yes 😄

Hehe, for sure. Originally (which is going back a long time now) I was quite resistant to the idea. But I’ve toyed with it from time to time, I think I’ll try a PoC to see how much better it works and how much work is involved.

Basically the alternative is a huge amount of work. One thing I was considering was to use TypeScript types for IDE functionality, I think they’re available for almost everything these days. But that still doesn’t work properly for e.g. navigation to source.

I see. Yes indeed. Other IDEs from what I know use LSP for all of that, but it would tax performance quite a bit. Here’s the scenario for a JS dev that also does clojure (which means semi dabling in java source from time to time) You either pay for intellij or buy webstorm. However intellij paid already has all of webstorm installed so you get a better deal with intellij at a cheaper price. This is why I didnt buy webstorm after my student license expired. What I’m trying to say with this is that people that work in the jet brains ecosystem, if they do clojurescript, most likely already have the paid intelliJ. Disclaimer: This is a conclusion from my individual experience and may not apply to others

Regarding to the PoC, I will gladly test it out for feedback if you like!!

i, for one, would want proper JS support even if it means it’s only available on the paid edition.

I'm interested in this. I have a typescript react UI layer in a reframe app using interop. If exported types were useful it would definitely be a DX upgrade

So there’s a recent issue which is similar to this, I commented on it here: https://github.com/cursive-ide/cursive/issues/2322#issuecomment-1097566491

However that doesn’t look exactly like your case.

Just checking, is your dev profile enabled in your REPL run config?

Yes, it is enabled (I'm able to run dev-specific fn in REPL). I think this looks like my problem. I need :repl-options 's :init and :init-ns functionality like leiningen has.