ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A decision guide to tRPC client transports: when httpBatchLink is enough, when streaming or SSE subscriptions earn their place, and how to route both through one splitLink client.
Background The htmx SSE extension maintains persistent server-sent event connections for real-time updates, but its reconnection behavior after browser tab restoration or network interruption relies on the browser's native EventSource implementation combined with htmx's reconnect configuration parameter. The core documentation does not formally specify recon
I am designing a page that combines two supported htmx components: the Server-Sent Events extension (sse-swap) and core's hx-swap-oob attribute. The server pushes fragments over SSE, and some fragments contain both a primary element and out-of-band children meant to update other parts of the DOM by id. My understanding is that the SSE extension hands the fra
htmx