mirror of
https://github.com/zebrajr/react.git
synced 2025-12-06 12:20:20 +01:00
36e4cbe2e9
Stacked on #26557 Supporting Float methods such as ReactDOM.preload() are challenging for flight because it does not have an easy means to convey direct executions in other environments. Because the flight wire format is a JSON-like serialization that is expected to be rendered it currently only describes renderable elements. We need a way to convey a function invocation that gets run in the context of the client environment whether that is Fizz or Fiber. Fiber is somewhat straightforward because the HostDispatcher is always active and we can just have the FlightClient dispatch the serialized directive. Fizz is much more challenging becaue the dispatcher is always scoped but the specific request the dispatch belongs to is not readily available. Environments that support AsyncLocalStorage (or in the future AsyncContext) we will use this to be able to resolve directives in Fizz to the appropriate Request. For other environments directives will be elided. Right now this is pragmatic and non-breaking because all directives are opportunistic and non-critical. If this changes in the future we will need to reconsider how widespread support for async context tracking is. For Flight, if AsyncLocalStorage is available Float methods can be called before and after await points and be expected to work. If AsyncLocalStorage is not available float methods called in the sync phase of a component render will be captured but anything after an await point will be a noop. If a float call is dropped in this manner a DEV warning should help you realize your code may need to be modified. This PR also introduces a way for resources (Fizz) and hints (Flight) to flush even if there is not active task being worked on. This will help when Float methods are called in between async points within a function execution but the task is blocked on the entire function finishing. This PR also introduces deduping of Hints in Flight using the same resource keys used in Fizz. This will help shrink payload sizes when the same hint is attempted to emit over and over again
43 lines
1.6 KiB
JavaScript
43 lines
1.6 KiB
JavaScript
/**
|
|
* Copyright (c) Meta Platforms, Inc. and affiliates.
|
|
*
|
|
* This source code is licensed under the MIT license found in the
|
|
* LICENSE file in the root directory of this source tree.
|
|
*
|
|
* @flow
|
|
*/
|
|
|
|
// This is a host config that's used for the `react-server` package on npm.
|
|
// It is only used by third-party renderers.
|
|
//
|
|
// Its API lets you pass the host config as an argument.
|
|
// However, inside the `react-server` we treat host config as a module.
|
|
// This file is a shim between two worlds.
|
|
//
|
|
// It works because the `react-server` bundle is wrapped in something like:
|
|
//
|
|
// module.exports = function ($$$config) {
|
|
// /* renderer code */
|
|
// }
|
|
//
|
|
// So `$$$config` looks like a global variable, but it's
|
|
// really an argument to a top-level wrapping function.
|
|
|
|
declare var $$$config: any;
|
|
export opaque type Destination = mixed; // eslint-disable-line no-undef
|
|
|
|
export opaque type PrecomputedChunk = mixed; // eslint-disable-line no-undef
|
|
export opaque type Chunk = mixed; // eslint-disable-line no-undef
|
|
|
|
export const scheduleWork = $$$config.scheduleWork;
|
|
export const beginWriting = $$$config.beginWriting;
|
|
export const writeChunk = $$$config.writeChunk;
|
|
export const writeChunkAndReturn = $$$config.writeChunkAndReturn;
|
|
export const completeWriting = $$$config.completeWriting;
|
|
export const flushBuffered = $$$config.flushBuffered;
|
|
export const close = $$$config.close;
|
|
export const closeWithError = $$$config.closeWithError;
|
|
export const stringToChunk = $$$config.stringToChunk;
|
|
export const stringToPrecomputedChunk = $$$config.stringToPrecomputedChunk;
|
|
export const clonePrecomputedChunk = $$$config.clonePrecomputedChunk;
|