app/entry.server.tsx

Functions

Imports

It imports app/lib/context.ts, app/lib/error-message.mjs. No module of this repo imports it.

Source

1import type { EntryContext, RouterContextProvider } from "react-router";
2import { ServerRouter } from "react-router";
3import { renderToReadableStream } from "react-dom/server";
4
5import { getNonce } from "~/lib/context";
6import { errorMessage } from "~/lib/error-message.mjs";
7
8export default async function handleRequest(
9  request: Request,
10  responseStatusCode: number,
11  responseHeaders: Headers,
12  routerContext: EntryContext,
13  // The request context `workers/app.ts` built and set `nonceContext` into (admin paths only).
14  loadContext: RouterContextProvider,
15) {
16  let shellRendered = false;
17
18  // The ServerRouter prop nonces React Router's streaming scripts; without it an enforcing CSP blocks
19  // the hydration payload. react-dom's own inline scripts take the nonce only from the render option.
20  // Undefined on public pages, which do not hydrate and stream no inline script of their own.
21  const nonce = getNonce(loadContext);
22
23  const body = await renderToReadableStream(
24    <ServerRouter context={routerContext} url={request.url} nonce={nonce} />,
25    {
26      nonce,
27      onError(error: unknown) {
28        responseStatusCode = 500;
29        // Errors before the shell renders reject and are logged in handleDocumentRequest.
30        if (shellRendered) {
31          console.error(JSON.stringify({ alert: "render-failed-after-shell", detail: errorMessage(error) }));
32        }
33      },
34    },
35  );
36  shellRendered = true;
37
38  // No `await body.allReady` for crawlers: the only Suspense boundary is on the admin plane. If a
39  // public route ever streams one, restore the wait, not a user-agent sniff.
40
41  responseHeaders.set("Content-Type", "text/html");
42  return new Response(body, {
43    headers: responseHeaders,
44    status: responseStatusCode,
45  });
46}