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

[hi-ogawa]

• related feat(react-server): preload client references #257

Looking back #257, the manifest manipulation looks too complicated, so I'm trying a new approach based on rollup's ModuleInfo.

We can solve this mapping in two steps:

# react-server build (routeManifestPluginServer)
# (mapping from server route to "use client" file id)
routes/page.tsx (server route) --(traverse ModuleInfo.imports)--> some-client.tsx (a file with "use client")

# browser build (routeManifestPluginClient)
# (mapping form "use client" file id to asset path)
some-client.tsx  ~(OutputBundle)~> assets/some-client-xxx.js (also follow Chunk.imports deeply)

todo

• build time
  • use transform.meta and PluginContext.getModuleInfo to map from route to client reference (during server build)
  • map client reference id to browser asset file (during browser build)
• runtime
  • this is probably unavoidable and just need to copy feat(react-server): preload client references #257
    separate PR?
• test

[hi-ogawa]

• fix(react-server): fix client css FOUC #342
• feat(react-server): preload css #341
• feat(react-server): preload client assets on navigation #340
• feat(react-server): preload client assets during ssr #337
• feat(react-server): generate mapping of server route to client assets #331 👈
• refactor(react-server): simplify route tree utils #338
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @hi-ogawa and the rest of your teammates on Graphite

[hi-ogawa]

Merge activity

• Jun 3, 11:09 PM EDT: @hi-ogawa started a stack merge that includes this pull request via Graphite.
• Jun 3, 11:10 PM EDT: Graphite rebased this pull request as part of a merge.
• Jun 3, 11:11 PM EDT: @hi-ogawa merged this pull request with Graphite.