Yes, that sounds like exactly it

wonder if that was cljc files as well? If I split things into clj/cljs files it seems ok, and it only seems to have a problem with the cljc macro syntax require sugar.

Ok, I’ll take a look - I haven’t had time to investigate either of them yet.

Ah, I remember now when this was happening earlier: I think it had to do with when I had those files in the jar more than once.

I think perhaps Cursive is seeing them twice and perhaps thinking there is a loop from one to the other and back again.

perhaps deps is somehow causing the lib to pull itself in through a transitive dep?

Interestingly, when I look at the external deps, I DO see a diff version of the lib I’m working on

@U0567Q30W That was it!

Updated the issue with my findings.

@tony.kay Oh, interesting - thanks!