React dev notes

[hi-ogawa]

TODO

• how to flow locally?
• how to keep old build and only rebuild react-server-dom-vite?

# build common deps (see yarn build-for-flight-dev) (not necessary?)
node ./scripts/rollup/build.js react/index,react/jsx,react.react-server,react-dom/index,react-dom/client,react-dom/server,react-dom.react-server,react-dom-server.node,react-dom-server-legacy.node,scheduler type=NODE_DEV

# how to keep old builds?
node ./scripts/rollup/build.js react-server-dom-vite/ --type=NODE_DEV

# copy to fixture
cp -rf build/node_modules fixtures/flight-vite/node_modules

---

• Which react-server-dom-xxx should we copy to start with?
  • probably react-server-dom-webpack or actually Jacob's manifest
• How to actually implement "invalidate-able" async module?
  • start with Jacobs manifest API and provide default one?
  • maybe we can just stash (mutate) it in ClientReference?
• about chunk preload
  • is server side reference module deps preload necessary?
    • actually there's no safe way to "preload" on server. running import(...) breaks execution order (since it's not a module factory chunk like webpack). so we cannot have server deps chunk preload.
    • rollup's hoistTransitiveImports is safe only because it's entry? https://rollupjs.org/configuration-options/#output-hoisttransitiveimports
  • for browser build, __vitePreload works equivalently (and it's safe since it only uses modulepreload), so we don't need that logic as well.
  • ssr prepare destination is desired, so we need to either
    • let server to provide client via resolveClientReferenceMetadata
      • rsc build needs access to browser build manifest.
      • this is the builtin prepare destination logic.
    • let ssr module loading to call ReactDOM.preloadModule instead of prepare destination logic.
      • ssr build needs access to browser build manifest, which is easier in general.

---

Can we have opinionated client/server references handling?

• assume Vite 6 environment API / module runner
• __vite_rsc_raw_import__ on client to workaround
• virtual:vite-rsc/client-references and virtual:vite-rsc/server-references
• virtual:vite-rsc/client-references to include asset deps