thoughts on external server component with internal client boundary

[hi-ogawa]

• fix: partial support of server-client-mixed package + chore: add react-tweet demo #384

Also the series of the issues related to client boundary resolution

• feat(react-server): expose external client reference via virtual module during dev #187
• fix(react-server): fix ?import query dual package when client module is used at both boundary and non-boundary #315
• fix(react-server): noramlize client reference with ?t= query (hmr timestamp) #316

todo

• is it possible to see the original import source during transform? (though this doesn't really help anything)
• is it possible to force stripping ?v=... certain dependenceis? (assuming they are not cjs and can put it in optimizeDeps.exclude)
• setup artificial packages to demonstrate issue (also test it on Next.js)
  • legitimate one (self referential exports)
  • shaky-but-works one (like react-tweet)
  • broken one
  • deep dep
• fully non-externalize deps
  • vendering? make it free from /node_modules/
• try virtual:normalize-url/... like in https://github.com/hi-ogawa/vite-environment-examples/blob/c08e7e7f697e5b0734940f4111735b4727c78049/examples/react-server/vite.config.ts#L216-L265