import { readFile } from "node:fs/promises"; import { defineConfig } from "vite"; import { getBuildConfig } from "./src/contracts/env.ts"; import { SERVICE_WORKER_CACHE_SCHEMA_VERSION, SERVICE_WORKER_PROTOCOL_VERSION, SERVICE_WORKER_SCRIPT_PATH, } from "./src/contracts/service-worker.ts"; import { INSTALLED_RUNTIME_CAPABILITIES } from "./src/features/installed-runtime-capabilities.ts"; import { runOutputPath } from "./scripts/lib/run-isolation.ts"; import { resolveServiceWorkerBuildInput } from "./scripts/lib/service-worker-build-input.ts"; /** * §17.2.2 step 5. The Service Worker build. * * Runs only when the static selection is `ACTIVE`, after the app build has * completed and the hashed asset list has been generated. `emptyOutDir` is * false so it adds `service-worker.js` beside the already-built app rather than * replacing it. */ const selection = INSTALLED_RUNTIME_CAPABILITIES.serviceWorker; // Relative to this file: Vite's default `bundle` config loader runs the config // from `node_modules/.vite-temp/`, so a bare `import("./.generated/...")` would // resolve there. Every loader keeps `import.meta.url` pointing at this file. // 1105/12-04. The generated modules, `dist/config.json` and the output are // under RUN_OUTPUT_ROOT when the build sets one (scripts/build-frontend.ts). async function readGenerated(path: string, exportName: string): Promise { try { const module = (await import(new URL(path, import.meta.url).href)) as Record< string, unknown >; if (!(exportName in module)) { throw new TypeError(`Generated module does not export ${exportName}.`); } return module[exportName] as T; } catch (error) { throw new TypeError(`Required generated module is unavailable: ${path}`, { cause: error, }); } } const assets = await readGenerated( `./${runOutputPath(".generated/frontend-runtime/service-worker-assets.ts")}`, "SERVICE_WORKER_ASSETS", ); const contractSet = await readGenerated<{ setDigest?: string }>( `./${runOutputPath(".generated/frontend-runtime/contract-set.ts")}`, "BUILD_CONTRACT_SET", ); // 06-10 / F-8. The profile document `scripts/generate-runtime-config.ts` wrote // in step 4, not `public/config.json`, which is always the local profile. const runtimeConfig = JSON.parse( await readFile(runOutputPath("dist/config.json"), "utf8"), ) as Record; const buildId = process.env.VITE_BUILD_ID ?? "local-build"; const releaseId = process.env.RELEASE_ID ?? "local-release"; const buildInput = resolveServiceWorkerBuildInput({ selection, assets, contractSet, runtimeConfig, appProfile: process.env.APP_PROFILE ?? "local", buildId, releaseId, }); export default defineConfig({ // 0929/06-01. `dist` already holds the app build, `public/` included. Copying // `public/` again would put the local `public/config.json` back over the // profile document step 4 wrote. publicDir: false, build: { outDir: runOutputPath("dist"), // §17.2.2: exactly one input, exactly one output, no additional chunk. emptyOutDir: false, sourcemap: false, rolldownOptions: { input: "src/adapters/service-worker/service-worker-entry.ts", output: { format: "es", inlineDynamicImports: true, entryFileNames: SERVICE_WORKER_SCRIPT_PATH, }, }, }, define: { __CA_SERVICE_WORKER_BUILD_INFO__: JSON.stringify({ serviceWorkerProtocolVersion: SERVICE_WORKER_PROTOCOL_VERSION, cacheSchemaVersion: SERVICE_WORKER_CACHE_SCHEMA_VERSION, buildId, releaseId, contractSetDigest: buildInput.contractSetDigest, staticAssetSetDigest: buildInput.assets.setDigest, }), __CA_SERVICE_WORKER_ASSETS__: JSON.stringify(buildInput.assets), __CA_SERVICE_WORKER_HANDLERS__: JSON.stringify(buildInput.handlers), // 0929/06-02. The page's own default, which follows the router base path. __CA_RUNTIME_CONFIG_URL__: JSON.stringify( getBuildConfig(process.env).runtimeConfigUrl, ), __CA_RELEASE_MANIFEST_URL__: JSON.stringify( buildInput.releaseManifestUrl, ), }, });