@rsc-kit/core 0.20.12 → 0.20.13

package/dist/vite.js

@@ -3903,9 +3903,20 @@ export async function handleRscResume(
   )
 
   const ssr = await (import.meta as any).viteRsc.loadModule('ssr', 'index')
-  const htmlStream = await ssr.handleSsrResume(flight, postponed, nonce)
+  // Whether React could replay the recorded tree at all. A bundler that
+  // merges scopes renames components, and a name is how React matches a
+  // slot: the same page, built once and bundled again - which is what
+  // bun build --compile does - has different names at runtime than the
+  // shell recorded. Reported so the host can stop resuming this shell and
+  // render the page whole, rather than serving one whose holes are all
+  // client-rendered. Set before the stream ends, because that is when
+  // React reports it.
+  let replayFailed = false
+  const htmlStream = await ssr.handleSsrResume(flight, postponed, nonce, () => {
+    replayFailed = true
+  })
 
-  return { htmlStream }
+  return { htmlStream, replayed: () => !replayFailed }
 }
 
 // Server action (worker: rsc-action).
@@ -4977,6 +4988,11 @@ export async function handleSsrResume(
   rscStream: ReadableStream,
   postponed: unknown,
   nonce?: string,
+  // Told when React refuses to replay: the tree it recorded and the tree
+  // rendering now put different components in a slot, so every hole below
+  // is client-rendered instead of filled here. The caller decides what to
+  // do about it; see the host.
+  onReplayMismatch?: () => void,
 ): Promise<ReadableStream> {
   const root = await createFromReadableStream(rscStream)
 
@@ -4987,7 +5003,13 @@ export async function handleSsrResume(
     // the designed path, on every resume of a shell whose hole holds one -
     // printed as "[rsc-kit:resume] Error: useSearchParams() was read..." on
     // every request, with advice the app had already followed.
-    onError: reportRenderError('resume'),
+    onError: (error: unknown, info: unknown) => {
+      const message = String((error as { message?: string } | null)?.message ?? error)
+
+      if (message.includes('instead it rendered') || message.includes('resumable slots')) onReplayMismatch?.()
+
+      return reportRenderError('resume')(error, info)
+    },
   })
 
   return DEV_ORIGIN ? rewriteViteDevUrlStream(html, DEV_ORIGIN) : html
@@ -6031,6 +6053,32 @@ export function rscKit(options = {}) {
                                 external: serverExternals,
                                 // Same table, same reason.
                                 checks: { ineffectiveDynamicImport: false },
+                                output: {
+                                    // One copy of a dependency, however many client components
+                                    // reach for it.
+                                    //
+                                    // Every client component is its own entry here - the SSR
+                                    // side of a client reference, imported by id - and a
+                                    // dependency two of them share is copied into each one's
+                                    // chunk group. Two copies of one component are two
+                                    // different functions, and that is fine until something
+                                    // merges the module scopes: `bun build --compile` does,
+                                    // renames the second copy, and a partially prerendered
+                                    // page records its tree BY COMPONENT NAME. The shell then
+                                    // says <J>, the binary renders <J2>, React refuses the
+                                    // replay and every hole falls to the browser - a page
+                                    // that arrives looking finished with nothing wired up. A
+                                    // port found it on one page, in production, on cold
+                                    // loads only.
+                                    //
+                                    // Grouping node_modules into one chunk means a shared
+                                    // dependency exists once, so there is nothing to collide.
+                                    // The server does not pay for the bigger chunk the way a
+                                    // browser would: it reads from disk, once, at startup.
+                                    advancedChunks: {
+                                        groups: [{ name: "vendor", test: /[\\/]node_modules[\\/]/ }],
+                                    },
+                                },
                             },
                         },
                         resolve: { noExternal: bundledClientPackages },