Files
tech-log-frontend/vite.config.ts
DongHyeonka ed47b562bc perf(build): react-dom을 자기 청크로 빼 빌드 id만 바뀐 배포의 캐시 손실을 줄인다
빌드 id는 부트 실패 화면이 보여 주므로 render-boot-failure 청크에
들어간다(getBuildConfig). react-dom과 scheduler가 같은 청크에 있어서
빌드 id만 다른 두 빌드에서 그 190,478 B 청크의 이름이 바뀌었다. 해시
자산은 오래 캐시되는데, 재방문 사용자는 코드가 같아도 배포마다 이만큼
다시 받았다. 단위 시험 build-environment-bundle이 이 청크가 바뀐다고
실패했다.

템플릿 af6d0a9f(1103/15-06)와 같은 방식이다. manualChunks에서 react-dom·
scheduler를 react-dom 청크로 뺀다. 시험은 템플릿 새 판처럼 디자인 시스템
청크를 이름 대신 내용(ui-button--pending)으로 찾아 고정됐는지 보고,
react-dom 청크가 고정이며 render-boot-failure가 아닌지 본다. 이전 시험은
빌드 id를 일부러 담는 render-boot-failure를 공용 청크로 잘못 골랐다.

위험·한계: 정규식은 pnpm의 node_modules 배치를 가정한다. 배치가 바뀌어
그룹이 비면 시험이 실패한다. boot(약 320 KB)는 빌드 id로 설정을 대조하므로
계속 이름이 바뀐다(템플릿과 같음).

검증: 빌드 id만 다른 두 빌드에서 이름이 바뀐 청크는 boot·index·
render-boot-failure 셋이고, render-boot-failure는 12,138 B로 줄었다.
react-dom 청크와 디자인 시스템 청크는 두 빌드에서 이름이 같다.
2026-11-12 12:50:28 +09:00

164 lines
7.7 KiB
TypeScript

import { defineConfig, loadEnv } from "vite";
import react from "@vitejs/plugin-react";
import tailwindcss from "@tailwindcss/vite";
import { viteModuleInventoryPlugin } from "./scripts/lib/vite-module-inventory.ts";
import { ENV_REGISTRY } from "./src/contracts/env.ts";
/**
* 13-06. Every VITE_* value Vite loads (shell or `.env*`) is public once
* something bundles it, so a value the build does not declare is refused
* rather than carried along.
*/
function assertDeclaredBuildVariables(mode: string): void {
const undeclared = Object.keys(loadEnv(mode, process.cwd(), "VITE_"))
.filter((name) => !Object.hasOwn(ENV_REGISTRY, name))
.sort();
if (undeclared.length > 0) {
throw new Error(
`Undeclared VITE_* build variables: ${undeclared.join(", ")}. ` +
"Declare them in ENV_REGISTRY (src/contracts/env.ts) or unset them; " +
"VITE_ values are published to the browser.",
);
}
}
const techLogRouteChunks = Object.freeze({
"/public/pages/home-page.tsx": "route-tech-log-home",
"/public/pages/explore-page.tsx": "route-tech-log-explore",
"/public/pages/explore-kind-page.tsx": "route-tech-log-explore-kind",
"/public/pages/case-page.tsx": "route-tech-log-case",
"/public/pages/reference-page.tsx": "route-tech-log-reference",
"/public/pages/concept-page.tsx": "route-tech-log-concept",
"/public/pages/setup-page.tsx": "route-tech-log-setup",
"/public/pages/question-page.tsx": "route-tech-log-question",
"/public/pages/topics-page.tsx": "route-tech-log-topics",
"/public/pages/topic-page.tsx": "route-tech-log-topic",
"/public/pages/topic-variant-page.tsx": "route-tech-log-topic-variant",
"/public/pages/projects-page.tsx": "route-tech-log-projects",
"/public/pages/project-overview-page.tsx": "route-tech-log-project",
"/public/pages/project-records-page.tsx": "route-tech-log-project-records",
"/public/pages/project-decisions-page.tsx": "route-tech-log-project-decisions",
"/public/pages/project-activity-page.tsx": "route-tech-log-project-activity",
"/public/pages/releases-page.tsx": "route-tech-log-releases",
"/public/pages/release-page.tsx": "route-tech-log-release",
"/public/pages/profile-page.tsx": "route-tech-log-profile",
"/public/pages/search-page.tsx": "route-tech-log-search",
"/studio/pages/studio-home-page.tsx": "route-tech-log-studio-home",
"/studio/pages/documents-page.tsx": "route-tech-log-studio-documents",
"/studio/pages/new-document-page.tsx": "route-tech-log-studio-document-new",
"/studio/pages/document-edit-page.tsx": "route-tech-log-studio-document-edit",
"/studio/pages/document-validation-page.tsx": "route-tech-log-studio-document-validation",
"/studio/pages/document-preview-page.tsx": "route-tech-log-studio-document-preview",
"/studio/pages/document-publish-page.tsx": "route-tech-log-studio-document-publish",
"/studio/pages/publications-page.tsx": "route-tech-log-studio-publications",
"/studio/pages/publication-preview-page.tsx": "route-tech-log-studio-publication-preview",
"/studio/pages/assets-page.tsx": "route-tech-log-studio-assets",
"/studio/pages/taxonomy-page.tsx": "route-tech-log-studio-taxonomy",
"/studio/pages/project-edit-page.tsx": "route-tech-log-studio-project-edit",
// 이 표를 빠뜨리면 빌드 매니페스트 단계에서 「Missing built route chunk」로 멈춘다.
// `route-chunk-names.test.ts` 가 다섯 검사 안에서 미리 대조한다.
"/studio/pages/topic-edit-page.tsx": "route-tech-log-studio-topic-edit",
"/studio/pages/releases-page.tsx": "route-tech-log-studio-releases",
"/studio/pages/release-edit-page.tsx": "route-tech-log-studio-release-edit",
"/studio/pages/studio-not-found-page.tsx": "route-tech-log-studio-not-found",
"/public/pages/public-not-found-page.tsx": "route-not-found",
} as const);
// pnpm lays packages out as node_modules/.pnpm/<name>@<version>/node_modules/<name>.
const REACT_DOM_MODULE =
/[\\/]node_modules[\\/](?:\.pnpm[\\/][^\\/]+[\\/]node_modules[\\/])?(?:react-dom|scheduler)[\\/]/;
function routeChunkName(moduleId: string): string | undefined {
const normalized = moduleId.replaceAll("\\", "/");
const featurePath = "/src/features/tech-log/presentation";
const featureIndex = normalized.lastIndexOf(featurePath);
if (featureIndex < 0) return undefined;
const routePath = normalized.slice(featureIndex + featurePath.length);
return techLogRouteChunks[routePath as keyof typeof techLogRouteChunks];
}
/**
* §6.1. One sub-path, declared once.
*
* `VITE_ROUTER_BASE_PATH` already drives the router and the Service Worker
* scope. Vite's asset `base` was left at its default, so a build served from
* `/app/` emitted root-absolute asset URLs and loaded nothing: the three
* consumers of the same setting disagreed. They are read from one value here so
* a sub-path deployment is coherent or fails at build time.
*/
function routerBasePath(environment: NodeJS.ProcessEnv): string {
const declared = environment["VITE_ROUTER_BASE_PATH"];
if (declared === undefined || declared === "") return "/";
if (!declared.startsWith("/") || !declared.endsWith("/")) {
throw new Error(
`VITE_ROUTER_BASE_PATH must start and end with "/"; received ${declared}`,
);
}
return declared;
}
/**
* 13-07. The runtime document ships inside dist, which is served under the
* base path. An explicit root-relative URL outside it would 404 at boot.
*/
function assertRuntimeConfigUnderBase(
environment: NodeJS.ProcessEnv,
base: string,
): void {
const declared = environment["VITE_RUNTIME_CONFIG_URL"];
if (declared?.startsWith("/") && !declared.startsWith(base)) {
throw new Error(
`VITE_RUNTIME_CONFIG_URL ${declared} is outside VITE_ROUTER_BASE_PATH ${base}`,
);
}
}
export default defineConfig(({ mode }) => {
assertDeclaredBuildVariables(mode);
const base = routerBasePath(process.env);
assertRuntimeConfigUnderBase(process.env, base);
return {
base,
plugins: [react(), tailwindcss(), viteModuleInventoryPlugin()],
build: {
manifest: true,
sourcemap: false,
/*
익명 독자가 여는 공개 화면의 HTML 에 Studio 청크 셋이 `modulepreload` 로 붙어 있었다 —
읽기만 하는 사람이 편집기 번들을 내려받았다.
`resolveDependencies` 는 주입되는 목록을 그대로 받는다. Studio 청크만 빼고 나머지는
그대로 둔다 — 공개 라우트의 미리 받기는 그 화면을 빨리 여는 데 실제로 쓰인다.
*/
modulePreload: {
resolveDependencies: (_filename, deps) =>
deps.filter((dep) => !dep.includes("route-tech-log-studio")),
},
// Template sync (af3d8e6). One chunking function under the key this
// product already builds with: the template's preload-helper split
// (09-03) first, then TechLog's named route chunks.
rolldownOptions: {
output: {
// 09-03. The entry now imports the app dynamically, so Vite's preload
// helper would land in the entry chunk and every lazy chunk would
// import the entry, whose hash changes with each build id.
//
// Template 1103/15-06 (af6d0a9f). react-dom and scheduler shared the
// boot-failure chunk with the build id (getBuildConfig), so a release
// that only changed the build id renamed that 190 KB chunk and
// returning visitors downloaded it again. In a chunk of their own they
// keep their name; only boot, the entry and the small boot-failure
// screen, which hold or import the build id, are renamed.
manualChunks: (id: string) =>
id.includes("vite/preload-helper")
? "preload-helper"
: REACT_DOM_MODULE.test(id)
? "react-dom"
: routeChunkName(id),
},
},
},
};
});