TODO: react-server

[hi-ogawa]

Follow up to

• chore: RSC experiment #172
• feat(react-server): create a package #178

vite concerns

• dual package with "use client" in node_modules. a few ideas to explore:
  • feat(react-server): expose external client reference via virtual module during dev #187
• dual package of client module used at client boundary and non-boundary
  • ?import query fix(react-server): fix ?import query dual package when client module is used at both boundary and non-boundary #315
  • ?t=... fix(react-server): noramlize client reference with ?t= query (hmr timestamp) #316
• external server component with client component inside
  • e.g. react-tweet <Tweet /> server component has <TweetInfoCreatedAt /> client component fix(react-server): support external server component with client component inside? #207
  • this case is not saved by feat(react-server): expose external client reference via virtual module during dev #187
• separate module graph for rsc "react-server" condition (vitePluginRscServer)
  • maybe switch SSR and RSC where SSR lives in a separate dev server?
  • use Vite environment API https://github.com/hi-ogawa/vite-environment-examples/tree/main/examples/react-server
• css
  • css from rsc feat(react-server): handle css in react-server #205
  • unocss/tailwind postcss integration
  • unocss vite integration refactor(react-server): simplify unocss vite integration #206
• 3rd party lib (should test at least one client component and server component)
  • Libraries that support React Server Components reactwg/server-components#6
  • client: react-wrap-balancer
  • server test(react-server): test 3rd party server component library #190
• crawl react 3rd party lib to setup ssr.optimizeDeps.include?
• client deps optimization discovery from rsc? "warmup" rsc? feat(react-server): setup client optimizeDeps.entries #245
• client hmr fails after rsc hmr test: more hmr tests #265

react-server concerns

• server action
  • as server props feat(react-server): server reference in rsc #176
  • as client import
  • callServer
  • progressive enhancement feat(react-server): progressive enhancement #183
  • action return value useFormState, useActionState
    • https://react.dev/reference/react-dom/hooks/useFormState#using-information-returned-by-a-form-action
    • https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations#server-side-validation-and-error-handling
    • Add React.useActionState facebook/react#28491
    • feat(react-server): action return value (implement useActionData) #255
  • action error?
    • for now redirect only, feat(react-server): server action redirect #248
  • closure server action and encryption?
• render full html via rsc
  • feat(react-server): render full html via RSC #203
• error response and boundary feat(react-server): client error boundary for server error #211
• __webpack_chunk_load__?
• moduleLoading?
• follow canary update
  • chore(react-server/deps): update react canary 14898b6a9-20240318 #209

framework concerns

• entry customizability
  • feat(react-server): custom react server entry #199 dev server side.
• obfuscating server/client reference id on build
  • feat(react-server): obfuscate reference id on production #201
  • should also hash together with name part of (id)::(name)
• more RouteProps
  • feat(react-server): add RouteProps.request #189
• router
  • rsc redirect feat(react-server): server component redirect #243
  • action redirect feat(react-server): server action redirect #248
  • single round trip redirection?
  • action pending state test(react-server): test ReactDom.useFormStatus #225
  • client router state integration feat(react-server): router transition state #224 refactor(react-server): simplify router store #227
• slim re-render, slim rsc stream
  • feat(react-server): keep common layout without re-rendering #231
• cookie session demo
  • feat(react-server): action redirect headers and context #254
• ssg, prerender
• prefetch link
  • feat(react-server): preload client references #257
• full client page (i.e. page.tsx with "use client") feat(react-server): serializable route props #262
• browser root error boundary / suspense to save crash?
• layout invalidation on server action
  • refactor(react-server): layout invalidation on server #266
• network error handling
  • currently client crashes whole thing if server is down?
• fix bugs found in chore: port demo react-server-demo-remix-tutorial#1
• "catch all" dynamic route feat(react-server): support catch-all dynamic route #301
• use official APIs
  • registerClientReference refactor(react-server): use official registerClientReference #285
  • registerServerReference
  • createServerReference refactor(react-server): use official createServerReference #283
  • encodeReply/decodeReply refactor(react-server): use official encodeReply/decodeReply/decodeAction/decodeFormState + feat: support useActionState #282
  • decodeAction refactor(react-server): use official decodeAction/decodeFormState #284
  • decodeFormState

chore

• port remix tutorial demo?
• study waku and vinxi
• remove unnecessary dynamic import round trip on client
  • react-server-dom-webpack/client.browser, client-reference.js: these two should be always included
  • module preload for known client references from SSR
• organize directory
  • employ rakkas's lib, runtime, features convention?
• refactor
  • split packages/react-server/src/plugin/index.ts
  • consistent global usage
    • __callServer, __history, __devServer, __rscDevServer, etc...
• make packages/react-server/examples/basic run-able outside of this monorepo
  • also run the same test on fresh install to avoid Vite's linked deps magic
  • test(react-server): test fresh install #188
• custom vite logger for rsc server
• e2e examples/starter
• test re-render count
• silence "use client" warning during build fix(react-server): silence false warning due to use client #221
• rename rsc, react-server -> server and server -> ssr
• implement own rsc-html-stream?
  • https://github.com/devongovett/rsc-html-stream
• setup changelog
• deploy vercel and cloudflare from CI

[hi-ogawa]

Closing as individual issues are created separately