Hendrik Liebau
@unstubbable.bsky.social
Software Engineer @vercel.com
That would need to be changed in React. With a Flight Client now also being used in the RSC layer, I believe there's a couple of places where the wording doesn't quite fit anymore. See also github.com/facebook/rea...
Rename SSRManifest to ServerConsumerManifest by sebmarkbage · Pull Request #31299 · facebook/react
This config is more generally applicable to all server-side Flight Clients and not just SSR.
github.com
October 25, 2024 at 12:34 PM
That would need to be changed in React. With a Flight Client now also being used in the RSC layer, I believe there's a couple of places where the wording doesn't quite fit anymore. See also github.com/facebook/rea...
The key can be created before initial render. The temporary references are created/resolved by their path in the args.
October 25, 2024 at 12:20 PM
The key can be created before initial render. The temporary references are created/resolved by their path in the args.
The cache key is generated using the Flight Reply Client, so the children are stable temporary references.
October 25, 2024 at 11:46 AM
The cache key is generated using the Flight Reply Client, so the children are stable temporary references.
It's powered by the same technique as x.com/sebmarkbage/....
Non-serialisable args like children are serialised as temporary references when the cached RSC payload is created. When the cached component is then called again, the temporary references are resolved back to the current args.
Non-serialisable args like children are serialised as temporary references when the cached RSC payload is created. When the cached component is then called again, the temporary references are resolved back to the current args.
x.com
x.com
October 25, 2024 at 11:43 AM
It's powered by the same technique as x.com/sebmarkbage/....
Non-serialisable args like children are serialised as temporary references when the cached RSC payload is created. When the cached component is then called again, the temporary references are resolved back to the current args.
Non-serialisable args like children are serialised as temporary references when the cached RSC payload is created. When the cached component is then called again, the temporary references are resolved back to the current args.