Hi there, if you’re just getting started and don’t have any particular reason to use figwheel, I’d stick with shadow CLJS. It’s easier to set up, actively maintained, and Thomas does an amazing job with support over in #C6N245JGG.

Of course, if you do need figwheel for some reason, let me know and I’ll help you out with that.

Thx for the answer, i will take a look into shadow-cljs this evening, is the shadowcljs repl easier to connect to from cursive?

Yes, I think so - it’s definitely a better-trodden path these days, and Thomas is also a Cursive user.

Well shadow-cljs works, and i can connect the nrepl, thats nice, but now i got all kinds of not resolved in cursive on every keyword

But it solves my asked problem i guess, if i have to decide i will prefer REPL over autocompletion and just ignore the "not resolved" highlights - REPL is just more important

How did you set your project up? Did you follow the suggestions here? https://shadow-cljs.github.io/docs/UsersGuide.html#_cursive

You can also keep your dependencies in a deps.edn file, import that into Cursive, and have shadow use that.