Files
tech-log-frontend/vite.config.ts
T
DongHyeonkaandClaude Opus 5 67a549173d feat: 축에 자기 화면을 준다
주제 화면의 네 줄(SPA·Mediator·BFF·Forward-Auth)은 링크인데 눌러도 아무 일이 없었다.
축의 주소를 주제 화면 안의 앵커로 잡아 두어서, 정작 주제 화면에서는 그 링크가 자기 자신을
가리켰다 — 주소만 바뀌고 화면은 그대로였다.

축에 화면을 준다. 결론을 먼저 두고 그 아래 그 축에 걸린 기록만 모은다. 목록 조회에
`variant` 필터를 더해 `record_variant` 로 거른다 — 축 slug 는 주제 안에서만 유일하므로
주제까지 함께 맞춘다.

정적 어댑터는 축으로 거르면 빈 목록을 준다. 축은 사람이 Studio 에서 거는 값이라 픽스처가
지어낼 수 없고, 없는 것을 있는 척하면 이 어댑터로 그린 화면이 서버로 바꿨을 때 달라진다.

`RecordFilters` 가 포트와 정적 어댑터에 따로 있어, 포트에 필터가 늘어도 이쪽은 모르는
상태가 됐다 — 메서드 매개변수가 bivariant 라 `satisfies` 가 잡지 못한다. 하나로 합친다.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011nAjrqNHGPNngN4aUbcyvJ
2026-09-01 20:36:53 +09:00

89 lines
4.4 KiB
TypeScript

import { defineConfig } from "vite";
import react from "@vitejs/plugin-react";
import tailwindcss from "@tailwindcss/vite";
import { viteModuleInventoryPlugin } from "./scripts/lib/vite-module-inventory.ts";
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/question-page.tsx": "route-tech-log-question",
"/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);
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;
}
export default defineConfig({
base: routerBasePath(process.env),
plugins: [react(), tailwindcss(), viteModuleInventoryPlugin()],
build: {
manifest: true,
sourcemap: false,
rolldownOptions: {
output: {
manualChunks: routeChunkName,
},
},
},
});