@tanstack/router-ssr-query-core@1.169.3

TanStack/router@tanstack/router-ssr-query-core@1.169.3Sep 16, 2026by github-actions[bot]

Upgrading?

AI Summary

This release introduces backpressure-aware transport for large deferred SSR payloads and improves error handling. It also updates the wire shape for `RawStream` arguments and refines Solid SSR behavior.

Key Highlights

  • Introduced backpressure-aware router transport for large deferred payloads
  • Improved error handling: 406 Not Acceptable for unsupported Accept headers
  • Updated JSON wire shape for `RawStream` arguments
  • Solid SSR now renders lazy errors through route boundaries
  • SSR Query integrations aligned with router lifecycle

Breaking Changes

  • JSON wire shape of `RawStream` server-function argument changed
  • Frame protocol constants moved from root to subpath

New Features

  • Backpressure-aware stream handling
  • Enhanced Solid SSR error rendering
  • Improved SSR Query stream ownership alignment

Full Release Notes

### Patch Changes

-   [#8204](https://github.com/TanStack/router/pull/8204) [`cbbfbe3`](https://github.com/TanStack/router/commit/cbbfbe37ab1dbe328c343cb437c5660769cc9f26) - Stream large deferred SSR hydration payloads through a backpressure-aware router transport, fail known setup errors before response creation, and close cancelled or expired transforms safely.

    Start now cancels discarded middleware and HEAD response bodies, including plain streams and derived branches.

    Server-function raw streams share one ordered response. Arbitrary or sequential consumption can require potentially unbounded buffering of unread data on the client. Cancelling one raw stream discards it locally, while aborting the whole call cancels the response and server work. Consume streams concurrently, cancel unused streams promptly, or use separate calls when independent backpressure is required. A raw stream that exceeds its unread-byte limit now fails alone; sibling streams and the JSON result keep flowing.

    The JSON wire shape of a `RawStream` server-function argument changed. Clients and servers must run matching versions for requests that pass a `RawStream`.

    The frame-protocol constants (`FRAME_TYPE_*`, `MAX_FRAME_PAYLOAD_SIZE`, `MAX_FRAMED_STREAMS`) moved from the `@tanstack/start-client-core` root to the `@tanstack/start-client-core/client-rpc` subpath.

    Router requests whose `Accept` header allows neither `text/html` nor `*/*` now receive `406 Not Acceptable` instead of `500`.

    Framework adapters share the body `<Scripts>` composition (`getSsrBodyScriptParts`, `composeSsrBodyScripts`) and the eager HTML response wrapper (`renderSsrHtmlResponse`) from `@tanstack/router-core`.

    Solid SSR now emits one document type and renders late lazy errors through route boundaries. A Solid `<Await>` without a `fallback` no longer holds the streamed shell; it renders inside the nearest `<Suspense>` boundary like React and Vue, and now renders falsy resolved values.

    Static server functions decode cached `RawStream` values with the client deserializer plugins.

    SSR Query integrations now keep request cleanup and stream ownership aligned with the router lifecycle.

Related Repositories