mirror of
https://github.com/zebrajr/react.git
synced 2025-12-06 12:20:20 +01:00
e81fcfe3f2
This is used to register Server References that exist in the current
environment but also exists in the server it might call into. Such as a
remote server.
If the value comes from the remote server in the first place then this
is called automatically to ensure that you can pass a reference back to
where it came from - even if the `serverModuleMap` option is used. This
was already the case when `serverModuleMap` wasn't passed. This is how
you can pass server references back to the server. However, when we
added `serverModuleMap` that pass was skipped because we were getting
real functions instead of proxies.
For functions that wasn't yet passed from the remote server to the
current server, we can register them eagerly just like we do for
`import('/server').registerServerReference()`. You can now also do this
with `import('/client').registerServerReference()`. We could make them
shared so you only have to do this once but it might not be possible to
pass to the remote server and the remote server might not even be the
same RSC renderer. Therefore I split them. It's up to the compiler
whether it should do that or not. It has to know that any function you
might call might be able to receive it. This is currently global to a
specific RSC renderer.
|
||
|---|---|---|
| .. | ||
| esm | ||
| npm | ||
| src | ||
| client.browser.js | ||
| client.js | ||
| client.node.js | ||
| index.js | ||
| package.json | ||
| README.md | ||
| server.js | ||
| server.node.js | ||
| static.js | ||
| static.node.js | ||
react-server-dom-esm
Experimental React Flight bindings for DOM using ESM.
Use it at your own risk.