mirror of
https://github.com/zebrajr/react.git
synced 2025-12-08 07:38:51 +01:00
5deb78223a
In #26624, the ability to mark a client reference module as `async` in the React client manifest was removed because it was not utilized by Webpack, neither in `ReactFlightWebpackPlugin` nor in Next.js. However, some bundlers and frameworks are sophisticated enough to properly handle and identify async ESM modules (e.g., client component modules with top-level `await`), most notably Turbopack in Next.js. Therefore, we need to consider the `async` flag in the client manifest when resolving the client reference metadata on the server. The SSR manifest cannot override this flag, meaning that if a module is async, it must remain async in all client environments. x-ref: https://github.com/vercel/next.js/pull/70022 |
||
|---|---|---|
| .. | ||
| npm | ||
| src | ||
| client.browser.js | ||
| client.edge.js | ||
| client.js | ||
| client.node.js | ||
| index.js | ||
| package.json | ||
| README.md | ||
| server.browser.js | ||
| server.edge.js | ||
| server.js | ||
| server.node.js | ||
| static.browser.js | ||
| static.edge.js | ||
| static.js | ||
| static.node.js | ||
react-server-dom-turbopack
Experimental React Flight bindings for DOM using Turbopack.
Use it at your own risk.