router-core/ssr

Server-side rendering with TanStack Router is set up by wiring a shared router and using defaultRenderHandler or defaultStreamHandler to render on both server and client environments. It provides APIs like createRequestHandler to manage requests.

Yes, TanStack Router supports streaming SSR through the renderRouterToStream API. It allows progressive rendering and proper hydration while managing loader dehydration and data serialization across environments.

Loader dehydration and hydration in TanStack Router SSR automatically serializes server-loaded data for the client. This ensures the client router hydrates with the exact same data state without duplicate network fetches.

Yes, document head management during server-side rendering is handled via the head route option for meta, links, styles, and scripts. The HeadContent and ScriptOnce components inject these elements across server and client.

renderRouterToString provides non-streaming server-side rendering by returning a complete HTML string, whereas renderRouterToStream enables streaming SSR for progressive rendering and faster initial document transmission.

Memory history is used on the server to manage TanStack Router routing state without a browser DOM. It integrates with createRequestHandler to process incoming URLs and render the correct route state.