test(rsc): run Parcel tests against production build (#13972)

Author: markdalgleish

integration/helpers/rsc-parcel/src/server.tsx

@@ -1,3 +1,4 @@
+import { parseArgs } from "node:util";
 import { createRequestListener } from "@mjackson/node-fetch-server";
 import express from "express";
 import { unstable_matchRSCServerRequest as matchRSCServerRequest } from "react-router";
@@ -71,7 +72,12 @@ app.use(
   )
 );
 
-const port = parseInt(process.env.RR_PORT || "3000", 10);
+const { values } = parseArgs({
+  options: { p: { type: "string", default: process.env.RR_PORT || "3000" } },
+  allowPositionals: true,
+});
+
+const port = parseInt(values.p, 10);
 app.listen(port, () => {
   console.log(`Server started on http://localhost:${port}`);
 });

integration/rsc/rsc-test.ts

@@ -46,9 +46,13 @@ const implementations: Implementation[] = [
     template: "rsc-parcel",
     build: ({ cwd }: { cwd: string }) => spawnSync("pnpm", ["build"], { cwd }),
     run: ({ cwd, port }) =>
-      // FIXME: Parcel prod builds seems to have dup copies of react in them :/
-      // Not reproducible in the playground though - only in integration/helpers...
-      implementations.find((i) => i.name === "parcel")!.dev({ cwd, port }),
+      createDev(["dist/server/server.js", "-p", String(port)])({
+        cwd,
+        port,
+        env: {
+          NODE_ENV: "production",
+        },
+      }),
     dev: ({ cwd, port }) =>
       createDev(["node_modules/parcel/lib/bin.js"])({
         // Since we run through parcels dev server we can't use `-p` because that