packages/react-server-dom-webpack/server.edge.js

/**
 * 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
 */

export {
  renderToReadableStream,
  decodeReply,
  decodeReplyFromAsyncIterable,
  decodeAction,
  decodeFormState,
  registerServerReference,
  registerClientReference,
  createClientModuleProxy,
  createTemporaryReferenceSet,
} from './src/server/react-flight-dom-server.edge';
Add Edge Server Builds for workerd / edge-light (#26116) We currently abuse the browser builds for Web streams derived environments. We already have a special build for Bun but we should also have one for [other "edge" runtimes](https://runtime-keys.proposal.wintercg.org/) so that we can maximally take advantage of the APIs that exist on each platform. In practice, we currently check for a global property called `AsyncLocalStorage` in the server browser builds which we shouldn't really do since browsers likely won't ever have it. Additionally, this should probably move to an import which we can't add to actual browser builds where that will be an invalid import. So it has to be a separate build. That's not done yet in this PR but Vercel will follow Cloudflare's lead here. The `deno` key still points to the browser build since there's no AsyncLocalStorage there but it could use this same or a custom build if support is added. 2023-02-07 15:10:01 -05:00			`/**`
			`* 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`
			`*/`

[Flight] reorganize code for forked entrypoints (#30702) This commit updates the file locations and bulid configurations for flight in preparation for new static entrypoints. This follows a structure similar to Fizz which has a unified build but exports methods from different top level entrypoints. This PR doesn't actually add the new top level entrypoints however, that will arrive in a later update. 2024-08-14 18:10:40 -07:00			`export {`
			`renderToReadableStream,`
			`decodeReply,`
[Flight] Support streaming of decodeReply in Edge environments (#31852) We support streaming `multipart/form-data` in Node.js using Busboy since that's kind of the idiomatic ecosystem way for handling these stream there. There's not really anything idiomatic like that for Edge that's universal yet. This adds a version that's basically just `AsyncIterable.from(formData)`. It could also be a `ReadableStream` of those entries since those are also `AsyncIterable`. I imagine that in the future we might add one from a binary `ReadableStream` that does the parsing built-in. 2024-12-19 12:54:59 -05:00			`decodeReplyFromAsyncIterable,`
[Flight] reorganize code for forked entrypoints (#30702) This commit updates the file locations and bulid configurations for flight in preparation for new static entrypoints. This follows a structure similar to Fizz which has a unified build but exports methods from different top level entrypoints. This PR doesn't actually add the new top level entrypoints however, that will arrive in a later update. 2024-08-14 18:10:40 -07:00			`decodeAction,`
			`decodeFormState,`
			`registerServerReference,`
			`registerClientReference,`
			`createClientModuleProxy,`
			`createTemporaryReferenceSet,`
			`} from './src/server/react-flight-dom-server.edge';`