Files
tech-log-frontend/vite.config.ts
T
DongHyeonka 0bb8f1df9c perf(build): design-system 모듈을 side effect 없음으로 선언한다
문제
공개 셸은 design-system/index.ts 배럴에서 Button 몇 개를 가져온다.
번들러는 배럴이 다시 내보내는 모듈을 side effect가 있다고 보고 모두
싣는다. 그래서 공개 첫 화면이 쓰지 않는 navigation·overlays·patterns
primitive와 폼 모듈(use-app-form 등)이 초기 JS에 있었다.

고른 방법
- 템플릿 1101/08-08(51941a54)과 같은 treeshake.moduleSideEffects 규칙을
  vite.config.ts에 둔다. 같은 vite 8.1.5다.
- design-system 파일은 선언만 하고 top-level 효과가 없다. 효과만을 위한
  import(`import "x"`)는 이 선언 아래에서 모듈과 같이 사라지므로,
  tests/unit/design-system-side-effects.test.ts가 그런 import가 없는지
  본다. CSS는 bootstrap/main.tsx에서 읽는다.
- 배럴을 통해서만 닿던 폼 모듈도 같이 빠진다. 폼 모듈에도 top-level
  효과가 없는 것을 확인했다.

위험·한계
- 초기 파일 수가 27개에서 28개로 는다. HTTP/2에서는 진입 청크의
  preload 목록으로 병렬로 받는다(템플릿 같은 판단).

검증
- desktop CI env 분석 빌드: 초기 JS 229,765 → 226,554 B(-3,211 B,
  분석 빌드 기준. 공식 수치는 예산 커밋).
2026-11-12 22:33:48 +09:00

195 lines
9.3 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): the template's chunk groups, then TechLog's
// named route chunks, in the template's `codeSplitting` form.
rolldownOptions: {
/*
템플릿 1101/08-08(51941a54)과 같다. design-system 모듈은 컴포넌트·아이콘·토큰 목록을
선언만 하고 top-level 효과가 없다. 그렇게 선언해 두면 공개 셸이 배럴(index.ts)에서
Button 하나를 가져와도, 아무 export 도 안 쓰인 primitive 파일은 초기 청크에서
빠진다. 효과만을 위한 import 를 두면 선언 아래에서 모듈과 같이 사라지므로 이 범위에는
그런 import 가 없다. CSS 는 bootstrap/main.tsx 에서 읽는다.
*/
treeshake: {
moduleSideEffects: [
{
test: /[\\/]src[\\/]presentation[\\/]design-system[\\/].+\.tsx?$/,
sideEffects: false,
},
],
},
output: {
codeSplitting: {
groups: [
// 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.
{ name: "preload-helper", test: /vite[\\/]preload-helper/ },
// 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.
{
name: "react-dom",
test: REACT_DOM_MODULE,
includeDependenciesRecursively: false,
},
// A route page gets its named chunk, its imports do not. The
// `manualChunks` function this replaces is a group that pulls
// every static dependency in: `route-not-found` took React, the
// i18n catalogs and installed-feature-messages.ts with it, and
// the boot-failure screen imports from that chunk. A module that
// threw while the application graph evaluated then took the
// boot-failure screen down too, and the static "loading" shell
// stayed up (boot-module-failure e2e, 09-03).
{
name: (id: string) => routeChunkName(id) ?? null,
includeDependenciesRecursively: false,
},
],
},
},
},
},
};
});