import { spawnSync } from "node:child_process"; import { rm, writeFile } from "node:fs/promises"; import process from "node:process"; import { SERVICE_WORKER_SCRIPT_PATH } from "../src/contracts/service-worker.ts"; import { INSTALLED_RUNTIME_CAPABILITIES } from "../src/features/installed-runtime-capabilities.ts"; import { makeDistFilesPublic } from "./lib/dist-permissions.ts"; import { runOutputPath } from "./lib/run-isolation.ts"; import { SELF_UNREGISTERING_SERVICE_WORKER } from "./lib/self-unregistering-service-worker.ts"; /** * §17.2.2. Deterministic two-pass build. * * The Service Worker needs the exact hashed asset list at compile time, so the * order is fixed: * * 1. clean dist and .generated/frontend-runtime * 2. generate contractSet and build-info source * 3. Vite app build (emptyOutDir = true) * 4. materialize dist/config.json from the declared APP_PROFILE * 5. scan app dist and generate the static asset source * 6. ACTIVE only: Vite Service Worker build (emptyOutDir = false, * publicDir = false: it must not copy `public/` over step 4, 0929/06-01) * REMOVE_REGISTRATION only: write the self-unregistering worker (06-03) * 7. generate Release Manifest V2 and the build manifest * 8. make every dist file readable by other users (13-02) * * Steps 5 and 6 are skipped for `REMOVE_REGISTRATION`, `PURGE_OWNED_RESOURCES` * and `null`: those modes never run an active worker build. * `REMOVE_REGISTRATION` still ships a `service-worker.js` so the browser's * update check can replace a worker that stops the page from booting (D-5). * * Step 4 has to follow the Vite build. Vite copies `public/` verbatim, so * without it every build — including a production one — ships the local * runtime document. The Service Worker asset scan excludes `config.json` * (`scripts/generate-service-worker-assets.ts`), so the order against step 5 * is not what keeps the profile out of the worker cache (13-15). Step 6 reads * the release manifest URL from the `dist/config.json` step 4 wrote, and fails * if its `APP_ENV` is not `APP_PROFILE` (06-10). * * 1105/12-04. With `RUN_OUTPUT_ROOT` set (a Playwright config sets it for its * web server under `TEST_RUN_ID`), every path above — `dist`, * `.generated/frontend-runtime` and the build's `artifacts/` evidence — is * under that folder instead, so a second build in the same checkout does not * empty the first one's `dist`. Every step reads the same variable * (`scripts/lib/run-isolation.ts`). Unset, the paths are the ones above. */ const selection = INSTALLED_RUNTIME_CAPABILITIES.serviceWorker; const buildsActiveWorker = selection?.mode === "ACTIVE"; const dist = runOutputPath("dist"); function run(command: string, args: readonly string[]): void { const result = spawnSync(command, [...args], { stdio: "inherit", env: process.env, }); if (result.status !== 0) { process.stderr.write(`build step failed: ${command} ${args.join(" ")}\n`); process.exit(result.status ?? 1); } } // 1. clean await rm(dist, { recursive: true, force: true }); await rm(runOutputPath(".generated/frontend-runtime"), { recursive: true, force: true }); // 2. contract set + build info run("node", ["scripts/generate-contract-set.ts"]); // 3. app build run("npx", ["vite", "build"]); // 4. runtime config for the declared profile run("node", ["scripts/generate-runtime-config.ts"]); if (buildsActiveWorker) { // 5. hashed asset inventory run("node", ["scripts/generate-service-worker-assets.ts", dist]); // 6. service worker build run("npx", ["vite", "build", "--config", "vite.service-worker.config.ts"]); } else if (selection?.mode === "REMOVE_REGISTRATION") { // 6. self-unregistering worker in place of the active one await writeFile( `${dist}/${SERVICE_WORKER_SCRIPT_PATH}`, SELF_UNREGISTERING_SERVICE_WORKER, ); } else { process.stdout.write( `service worker mode ${selection?.mode ?? "null"}: skipping worker build\n`, ); } // 7. release + build manifest run("node", ["scripts/generate-build-manifest.ts"]); // 8. publishable permissions: the validated writer creates 0600 files await makeDistFilesPublic(dist);