feat(react-server): preload client references

[hi-ogawa]

Demo screenshot

The bottom one shows hovering /test/deps is triggering client reference assets before fetching rsc.

todo 2

• Is it possible to collect client boundary by resolveId importer? I feel we shouldn't technically need lazy import glob to get this feature
• or we can entirely replace assets preloading with rsc prefetching, so that server only needs to figure out relevant client assets during runtime?

todo

• make server glob routes lazy so it's easier to collect per-route information from vite manifest?
  • lazy loading should help react server startup too.
• build time
  • disable client reference id hashing for easier debugging?
  • serve route to client reference mapping
  • client reference to js/css assets mapping
  • route tree
• runtime
  • route tree matching util
  • ssr preload
    • render from react-server via preload api?
    • actually this is not necessary if we setup bundler config chunks?
  • pass manifest to client
  • client preload
    • use react preload api? https://react.dev/reference/react-dom/preload
• also preload obviously known client dynamic deps (client-reference.js and react-server-dom-webpack/client.browser)
• test
• refactor

[hi-ogawa]

I'm hesitant to land this feature, so let's split a bit

• fix(react-server): preload root js assets #277
• lazy import glob feat(react-server): dynamic import glob routes #278
• tree utils refactor
• ssr preload
  • can track client reference during ssr and emit to body later?
  • still needs to probe manifest to find the assets
• client link preload intent

[hi-ogawa]

This will be superseded by

• feat(react-server): generate mapping of server route to client assets #331

Put this in draft for now