skills.rest
cill-i-am
cill-i-amCOMMUNITY
Explore all skills by this author →
𝕏@cillo_bGitHub

router-core/ssr

Coordinate server-client SSR for TanStack Router across streaming and non-streaming workflows.

Updated Apr 1, 2026
Search Tags:#react#streaming#ssr#hydration#tanstack-router#server-rendering#head-management
One-click install
npx skills add https://github.com/cill-i-am/task-tracker --skill router-core-ssr-cill-i-am
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: router-core/ssr
Source: https://github.com/cill-i-am/task-tracker/tree/main/.agents/skills/tanstack-router-ssr
Command: npx skills add https://github.com/cill-i-am/task-tracker --skill router-core-ssr-cill-i-am

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TanStack Router SSR setup coordinates server and client rendering across non-streaming and streaming workflows, providing unified RouterClient/RouterServer integration and document head management.

Core Features & Use Cases

  • Non-streaming SSR and Streaming SSR support with RouterClient/RouterServer
  • Memory history on the server and automatic data dehydration/hydration
  • Document head management via HeadContent/Scripts
  • Server/client entry points with renderRouterToString/renderRouterToStream
  • Reusable patterns suitable for TanStack Router apps

Quick Start

Create a shared router and wired server/client entries, then render with the appropriate SSR handler to hydrate on the client.

Frequently Asked Questions about router-core/ssr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up TanStack Router SSR with both streaming and non-streaming rendering?▼

TanStack Router SSR setup coordinates server and client rendering across non-streaming and streaming workflows using a shared router factory and SSR handlers like defaultRenderHandler or defaultStreamHandler to unify rendering end-to-end.

What do I need for TanStack Router hydration on the client after server rendering?▼

TanStack Router hydration requires a shared router factory, correct server and client entry setup, and SSR handlers like renderRouterToString or renderRouterToStream to enable automatic data dehydration and hydration with memory history on the server.

Does TanStack Router support document head management during server-side rendering?▼

TanStack Router SSR supports document head management via HeadContent and Scripts components, allowing you to manage head elements across server and client environments during server-side rendering and hydration.

What is the difference between renderRouterToString and renderRouterToStream for TanStack Router SSR?▼

renderRouterToString handles non-streaming SSR while renderRouterToStream handles streaming SSR in TanStack Router, both providing RouterServer and RouterClient integration with automatic data dehydration and hydration.

Can I use TanStack Router SSR without a shared router factory?▼

TanStack Router SSR requires a shared router factory to coordinate server-client rendering and unify non-streaming and streaming workflows, ensuring correct server and client entry setup for proper hydration.

Related Skills

Explore More Software Engineering Skills→
TanStackTanStack
14.9k

router-core/ssr

Configure non-streaming and streaming SSR for TanStack Router applications.

Official
Advanced
jcsoftdevjcsoftdev

streaming-ssr

Stream server-rendered HTML with React 18 streaming APIs to reduce TTFB and FCP.

Community
Advanced
tenequmtenequm
32

tanstack

Build type-safe React applications with TanStack Query, Router, and Start.

Community
Advanced
rezicsrezics
6

router-core/ssr

Execute TanStack Router loaders on server and client for universal rendering and data hydration.

Official
Advanced