refactor(rsc): load client reference without vite preload

[hi-ogawa]

• Closes https://github.com/users/hi-ogawa/projects/4/views/1?pane=issue&itemId=109578641

Entirely removing __vite__mapDeps and __vitePreload means that we give up supporting lazy preload and css for dynamic import inside client boundary. But this is probably reasonable since we expect client boundary as js/css code splitting boundary.

todo

• disable __vite__mapDeps entirely and test (by patching out vite:build-import-analysis?)
  • cf. Option to disable CSS preloading vitejs/vite#19505
• manage js chunks preload per client reference on our own
  • test
• manage css per client reference on our own
  • test
• move off client virtual from main browser bundle
  • do the same for ssr? it should still be able to bundle server easily as extra adapter build pass.
    • how does xxxpack/parcel allow post-bundling e.g. for cloudflare deploy? wouldn't their "chunk load" break? (e.g. parcelRequire.load(chunk)?)
      • Parcel has import "(server-dep-chunk)" hoisted to entry, so post-bundler can detect. Even though import(url) used by parcelRequire.load is not statically analyzable, wrangler can handle dynamic import as long as chunks are detected for deployment.
      • it likely breaks for other "common" adapter bundling solution.
      • also dynamic import is eagerly loaded, so it doesn't benefit from code splitting of client/server references on server.
    • react-server-dom-webpack patches __webpack_require__.u to overwrite chunk loading logic from flight payload.
  • ssr id re-mapping shouldn't be done by chunk file name level e.g. users might merge multiple client reference chunks for browser build but not on ssr build.
  • do the same for server reference?
• test dynamic import inside client boundary
• refactor
• update @hiogawa/react-server
• What if vite doesn't have __vite__mapDeps perf: reduce preload marker markup size vitejs/vite#14550 and have dependent chunks inline like before that PR? That would essentially avoid baking client chunks in main browser bundle and dependency chunks are only encoded in each chunk itself. Wouldn't that approach technically equivalent in terms of "rsc spirit"?
  • can we do the same on userland? maybe in this style? fix: apply __vitePreload correctly and when necessary vitejs/vite#19722
• what about dev?

[hi-ogawa]

• chore(rsc): custom client chunk example #904
• refactor(rsc): load client reference without vite preload #891 👈 (View in Graphite)
• main

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