Support initial serialized page data with client-only rendering #2287

Duplicates

• I searched existing issues. The closest is [Feature?]: disable ssr for some pages #1934, but that requests disabling SSR per page.

Summary 💡

I want to avoid hydration without creating an initial fetch waterfall for route props.

Currently:

• ssr: true sends props with the initial response, but also renders application HTML and requires hydration.
• ssr: false avoids hydration, but createAsync() / query() data is fetched after the client boots.

Requested mode:

• Resolve route data on the server.
• Return an HTML shell, client scripts, and serialized initial props in one response.
• Do not render application HTML on the server.
• Seed the client with those props and use render() instead of hydrate().

This resembles the Inertia page object: the initial response carries the matched component, props, URL, and version so the client can render immediately.

Motivation 🔦

Avoid maintaining hydration while preserving one request for both the document and its initial data. No duplicate server/client HTML rendering and no follow-up request waterfall for initial props.