189f70e17b
We currently have an awkward set up because the server can be used in two ways. Either you can have the server code prebundled using Webpack (what Next.js does in practice) or you can use an unbundled Node.js server (what the reference implementation does). The `/client` part of RSC is actually also available on the server when it's used as a consumer for SSR. This should also be specialized depending on if that server is Node or Edge and if it's bundled or unbundled. Currently we still assume Edge will always be bundled since we don't have an interceptor for modules there. I don't think we'll want to support this many combinations of setups for every bundler but this might be ok for the reference implementation. This PR doesn't actually change anything yet. It just updates the plumbing and the entry points that are built and exposed. In follow ups I'll fork the implementation and add more features. --------- Co-authored-by: dan <dan.abramov@me.com> |
||
|---|---|---|
| .. | ||
| esm | ||
| client.browser.js | ||
| client.edge.js | ||
| client.js | ||
| client.node.js | ||
| client.node.unbundled.js | ||
| index.js | ||
| node-register.js | ||
| plugin.js | ||
| server.browser.js | ||
| server.edge.js | ||
| server.js | ||
| server.node.js | ||
| server.node.unbundled.js | ||