rsbuild-plugin-react-router 0.6.6 → 0.7.1

package/src/rsc-virtual-modules.ts

@@ -1,7 +1,7 @@
 import { relative, resolve } from 'pathe';
 import type { Config } from './react-router-config.js';
 import type { Route } from './types.js';
-import { combineURLs, normalizeAssetPrefix } from './plugin-utils.js';
+import { normalizeAssetPrefix } from './plugin-utils.js';
 import { getVirtualModuleFilePath } from './virtual-modules.js';
 import {
   createRscInternalClientModule,
@@ -19,6 +19,7 @@ const RSC_VIRTUAL_ALIAS_IDS = [
   'allowed-action-origins',
   'client-version',
   'react-router-serve-config',
+  'manifest-prefix',
   'bootstrap-scripts',
   'server-manifest',
 ] as const;
@@ -29,8 +30,6 @@ type RscVirtualModulesOptions = {
   basename: string;
   buildDirectory: string;
   isBuild: boolean;
-  /** Resolved web `output.distPath.js` segment, e.g. `static/js`. */
-  jsDistPath: string;
   outputClientPath: string;
   publicPath: string;
   routeDiscovery: Config['routeDiscovery'];
@@ -73,7 +72,6 @@ export const createReactRouterRscVirtualModules = ({
   basename,
   buildDirectory,
   isBuild,
-  jsDistPath,
   outputClientPath,
   publicPath,
   routeDiscovery,
@@ -84,7 +82,10 @@ export const createReactRouterRscVirtualModules = ({
     resolve(buildDirectory, 'server'),
     outputClientPath
   );
-  const bootstrapPublicPath = normalizeAssetPrefix(publicPath);
+  // Absolute prefix the server must use for initial asset URLs (see
+  // `resolveEffectiveAssetPrefix`); the browser compiler may itself be on
+  // `'auto'`, which no server-rendered URL can express.
+  const serverPublicPath = normalizeAssetPrefix(publicPath);
 
   return {
     'virtual/react-router/unstable_rsc/routes': createRscRouteConfig({
@@ -111,9 +112,59 @@ export const createReactRouterRscVirtualModules = ({
         assetsBuildDirectory: rscAssetsBuildDirectory,
         publicPath,
       }),
-    'virtual/react-router/unstable_rsc/bootstrap-scripts': defaultExport([
-      combineURLs(bootstrapPublicPath, `${jsDistPath}/index.js`),
-    ]),
+    // Every server-facing asset URL in the rspack RSC manifest -- bootstrap
+    // `entryJsFiles`, route `entryCssFiles`, client references' `cssFiles`
+    // (react-server-dom-rspack renders those as <link>s), and Flight's
+    // `moduleLoading.prefix` for client-chunk preloads -- carries the browser
+    // compiler's public path, recorded in `moduleLoading.prefix`. With the
+    // browser compiler on `'auto'` rspack records `/`, which the server cannot
+    // serve from. `__rspack_rsc_manifest__` is this same object, so aligning
+    // it once, in place (arrays are mutated, not replaced, because
+    // `createServerEntry` has already captured references), makes every
+    // consumer agree on the server prefix without stacking a second one. The
+    // aligned manifest is exported (not imported for side effects only) so a
+    // `sideEffects: false` package cannot tree-shake the alignment away.
+    'virtual/react-router/unstable_rsc/manifest-prefix': `const manifest = __webpack_require__.rscM;
+const serverPrefix = ${JSON.stringify(serverPublicPath)};
+const appliedPrefix = manifest?.moduleLoading?.prefix;
+// An empty applied prefix (web \`assetPrefix: ''\`) yields relative references
+// such as "static/js/index.js"; those are rebased too, while absolute and
+// protocol-relative URLs are left alone.
+const isAbsoluteUrl = url => /^(?:[a-z][a-z\\d+.-]*:|\\/\\/|\\/)/i.test(url);
+if (typeof appliedPrefix === "string" && appliedPrefix !== serverPrefix) {
+  const rewrite = url =>
+    typeof url !== "string"
+      ? url
+      : appliedPrefix !== "" && url.startsWith(appliedPrefix)
+        ? serverPrefix + url.slice(appliedPrefix.length)
+        : appliedPrefix === "" && !isAbsoluteUrl(url)
+          ? serverPrefix + url
+          : url;
+  const rewriteAll = list => {
+    if (Array.isArray(list)) for (let i = 0; i < list.length; i++) list[i] = rewrite(list[i]);
+  };
+  manifest.moduleLoading.prefix = serverPrefix;
+  rewriteAll(manifest.entryJsFiles);
+  for (const files of Object.values(manifest.entryCssFiles ?? {})) rewriteAll(files);
+  for (const reference of Object.values(manifest.clientManifest ?? {})) rewriteAll(reference.cssFiles);
+}
+export const rscManifest = manifest;
+`,
+    // The compiled browser entry scripts come from the manifest (like Next's
+    // `buildManifest` or the Vite plugin's `loadBootstrapScriptContent`), so
+    // hashed entry filenames resolve without any naming contract. The list and
+    // its order are preserved. An empty list is a build problem (rspack only
+    // records entry files named `*.js`); fail loudly instead of guessing a
+    // filename that would render a document which cannot hydrate.
+    'virtual/react-router/unstable_rsc/bootstrap-scripts': `import { rscManifest } from "virtual/react-router/unstable_rsc/manifest-prefix";
+const entryJsFiles = rscManifest?.entryJsFiles;
+if (!entryJsFiles?.length) {
+  throw new Error(
+    "[rsbuild-plugin-react-router] The rspack RSC manifest lists no browser entry script (entryJsFiles is empty), so the server cannot render bootstrap scripts. Rspack only records entry files whose name ends in \\".js\\"; web output.filename.js values with a query (for example \\"[name].js?v=[contenthash:8]\\") or another extension are not supported in RSC mode."
+  );
+}
+export default entryJsFiles;
+`,
     'virtual/react-router/unstable_rsc/server-manifest': `export default function getServerManifest() {
   return __webpack_require__.rscM?.serverManifest;
 }