mirror of
https://github.com/zebrajr/react.git
synced 2025-12-07 12:20:38 +01:00
This is a follow-up from #30528 to not only handle props (the critical change), but also the owner ~and stack~ of a referenced element. ~Handling stacks here is rather academic because the Flight Server currently does not deduplicate owner stacks. And if they are really identical, we should probably just dedupe the whole element.~ EDIT: Removed from the PR. Handling owner objects on the other hand is an actual requirement as reported in https://github.com/vercel/next.js/issues/69545. This problem only affects the stable release channel, as the absence of owner stacks allows for the specific kind of shared owner deduping as demonstrated in the unit test. |
||
|---|---|---|
| .. | ||
| esm | ||
| npm | ||
| src | ||
| client.browser.js | ||
| client.edge.js | ||
| client.js | ||
| client.node.js | ||
| client.node.unbundled.js | ||
| index.js | ||
| node-register.js | ||
| package.json | ||
| plugin.js | ||
| README.md | ||
| server.browser.js | ||
| server.edge.js | ||
| server.js | ||
| server.node.js | ||
| server.node.unbundled.js | ||
| static.browser.js | ||
| static.edge.js | ||
| static.js | ||
| static.node.js | ||
| static.node.unbundled.js | ||
react-server-dom-webpack
Experimental React Flight bindings for DOM using Webpack.
Use it at your own risk.