shadow is proving to be challenging with inconsistent dependency availability, any recommendations of one over the other with shadow, figwheel or main?
maybe my real issue is cljs-ajax and cljs-http don’t support cljrn?
cljs-ajax was problematic for me; there was a solution of sorts somewhere but I preferred to go barebones and just use the React Native’s fetch API directly, that worked well enough for my use-case
seems like cljs-http supports cljsrn 😕 https://github.com/r0man/cljs-http/issues/122
at least for him
😆
As far as I remember cljs-http was fine; but I haven’t tried using it recently
i keep running into this with both libraries: https://clojurians.slack.com/archives/C6N245JGG/p1593717903181600
i’m suspicious of shadow so i’m switching to lein
I have no idea about shadow, perhaps ask in #shadow-cljs
that’s where that message was from, but they’re not sure over there either 😞
ah… I’d suggest just trying fetch api directly
If you don’t need advanced features, it will be more than good enough
I use this so I can auto-magically convert JS promises to core.async https://github.com/jamesmacaulay/cljs-promises has been working without issues for many years now
@benny cljs-http does work on RN (I’ve used it with both re-natal and Krell, but not shadow)
I think cljs-ajax does not
my main issue right now is the reference error above
I suspect it could be shadow causing the issue but haven't worked in figwheel or krell for cljs