Files
Andrew Clark 9e7b2782c7 [Flight] Server References for arbitrary object types
Added behind a new experimental flag, `enableFlightObjectReferences`.

Extends Server References so that a reference can point to an object,
not just a function. An object is registered with a new API,
`registerServerObjectReference`, which tags it with its module id the
same way `registerServerReference` tags a Server Function.

The client receives an opaque handle: reading a property or calling it
throws, similar to how Temporary References work inside Server
Functions. The only thing the client can do with the handle is pass it
back to the server via a Server Function, where it resolves through the
server manifest.

The motivating use case is letting a framework pass request-scoped
values by reference, so it can omit them from the request body. For
example, a framework could model `searchParams` as a module export
whose value resolves from the current request. This avoids encoding the
search params twice (they already appear in the request URL) but it
also makes the responses more cacheable: if the search params don't
appear elsewhere in the body, then a response cache can omit them from
its cache key.

This initial PR only exposes the new API in the Turbopack bindings. We
will port it to the other bundler configs if the experiment advances.
2026-09-16 23:08:48 -04:00
..
2020-03-07 11:23:30 -08:00

react-client

This is an experimental package for consuming custom React streaming models.

Its API is not as stable as that of React, React Native, or React DOM, and does not follow the common versioning scheme.

Use it at your own risk.