Clojurians Log v2

I think we were talking at cross purposes, it's totally on me, not making myself clear. The idea would be so that I don't have to manually work out all the kinks related to renderToPipeableStream myself. for example, after 3 months now, I returned to this, and while the initial page load works just fine, I can hydrate, etc. Hot reload (with shadow-cljs) doesn't. I don't yet know what the problem is, but probably 3 more months until I have time again...

like, i have this after page load

(when nil? @container (reset! root (createRoot @container)))

🤯

at page load, so no hot-reload yet

it just makes no sense why this is happening

Well, the code is wrong. Also the container should be defonce

I still don’t see how this could help with your issues.

Sorry, root creation should be defonced

what do you mean how this could help 🙂

and i realized that i need defonce, but that alone is not fixing this error

thanks either way. I appreciate it

UIx and Helix are the most popular ones

I know, but sadly it's been a long time when I could find any correlation between popularity and corner cases being supported 🙂 I was hoping maybe someone can speak from experience. I managed to set up reagent but these inconsistencies make all the work dubious now.

both are thin wrappers around React, including support for v18, that's the only requirement needed to be able to use renderToPipeableStream

even if none of them wrap and expose renderToPipeableStream, it's still possible to use the function by requiring React directly and calling react/renderToPipeableStream

of course, but then I am creating code I need to maintain myself, and it will be between two external dependencies so that's a bit too much risk for some applications that I just want to write and forget

well, it's literally a single function call that doesn't require any gluing code, I don't see how it can be risky

if renderToPipeableStream gets a breaking change in the future in React, the same will happen in the wrapping libraries

helix doesn't have any code that wraps react-dom/client or react-dom/server, and may not ever. it's expected that helix helps creating components and elements, and how you render them (dom server, dom client, react native, etc.) is your code

Roman's totally right that calling renderToPipeableStream is as low amount of coupling as you can get.