chore: readme

examples/child-process/README.md

@@ -1,11 +1,17 @@
 # child-process
 
-Running module runner inside child process (e.g. node, bun) with `--conditions react-server`, which allows `react` to be externalized.
+Custom environment to run a module runner inside a child process (e.g. node, bun). For example, this allows externalizing `react` deps by running a child process with `--conditions react-server`.
 
 ```sh
 pnpm dev
 ```
 
+## todo
+
+- write a summary
+  - why bridge server instead of vite server middleware
+  - `dispatchFetch(request)` vs `dispatchFetch(entry, request)`
+
 ## related
 
 - https://github.com/netlify/netlify-vite-environment

examples/child-process/src/entry-ssr.tsx

@@ -4,7 +4,6 @@ import React from "react";
 import ReactDomServer from "react-dom/server.edge";
 import ReactClient from "react-server-dom-webpack/client.edge";
 import type { StreamData } from "./entry-rsc";
-import type { ChildProcessFetchDevEnvironment } from "./lib/vite/environment";
 
 export default async function handler(request: Request): Promise<Response> {
   const url = new URL(request.url);
@@ -48,8 +47,6 @@ export default async function handler(request: Request): Promise<Response> {
   return new Response(ssrStream, { headers: { "content-type": "text/html" } });
 }
 
-declare const __vite_environment_rsc__: ChildProcessFetchDevEnvironment;
-
 async function handleRsc(request: Request): Promise<Response> {
   return __vite_environment_rsc__.dispatchFetch("/src/entry-rsc.tsx", request);
 }

examples/child-process/src/lib/ambient.d.ts

@@ -0,0 +1,2 @@
+declare const __vite_server: import("vite").ViteDevServer;
+declare const __vite_environment_rsc__: import("./vite/environment").ChildProcessFetchDevEnvironment;