chore: sync the frontend template from ebea300 to af3d8e6
Carries 359 template commits, tag v0.2.0 plus one documentation commit: the generator-built feature index with its app, bounded-context and feature declarations, the src/platform kernel and scale tooling, the 2026-09-24 src review fixes, and the 2026-09-25 maturity review round with its CHANGELOG [보안]/[계약] rows. 691 of the 824 template paths are applied, 85 of them merged with product changes; 127 are not carried. Product identity is unchanged: name, version 0.1.0, routes, design and the TechLog domain. Three decisions worth naming. TechLog stays composed directly, as the last two syncs recorded; its directory carries a NOT_INSTALLED marker that says so, and every installed-* composer takes the template's projection with TechLog added on top. The reference sample is no longer installed: the template now installs a feature only through feature-module.ts and context-routes.ts, which load the screens this product deleted, so its three operations, six schemas and one topic leave the registries, recorded as registry change evidence. And AppRouter mounts the platform and TechLog routes only; the template's bounded-context route gateway waits for a generator-installed feature. Required fixes: readSubject on the BFF session owner (without it every HTTP Studio session would close as integration-failed), zod through the facade in nine TechLog files, noUnusedLocals, and public/config.json written out to match the local profile. Derived baselines were recomputed after reproducing both sides' values: CI contract 101 commands / 106 references / 141 artifacts, gate shape c9adcf85; registry approval 2dc6c3a3; the runtime config schema baseline equals the schema at8210d48. Verified here: types, lint, architecture, adapter inventory, CI contract, i18n, design system, diagnostics, browser security, dev release manifest, TechLog contract and build pass; 220 component, 155 integration, 15 contract, 418 TechLog, 43 reference-feature, 18 recipe and 46 release-coherence tests pass, and 2381 of 2383 unit tests. Reproduced at8210d48first and unchanged: check:registries (byte-identical), test:runtime-schema, verify:documentation. Brought by the template and escalated rather than suppressed: check:request-fanout on TechLog's cursor pagination, check:remediation-ledger (fails upstream too), the shared-chunk hash test, and the registry-dependent sample removal and second-feature tests. Playwright suites were not run. Full record, the five open questions and the follow-ups in docs/operations/template-sync-2026-09-29.md. (cherry picked from commit b2170cf265dea45dc9cc05d3c61e627e97f31cdb)
This commit is contained in:
+70
-21
@@ -1,8 +1,27 @@
|
||||
import { defineConfig } from "vite";
|
||||
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",
|
||||
@@ -75,27 +94,57 @@ function routerBasePath(environment: NodeJS.ProcessEnv): string {
|
||||
return declared;
|
||||
}
|
||||
|
||||
export default defineConfig({
|
||||
base: routerBasePath(process.env),
|
||||
plugins: [react(), tailwindcss(), viteModuleInventoryPlugin()],
|
||||
build: {
|
||||
manifest: true,
|
||||
sourcemap: false,
|
||||
/*
|
||||
익명 독자가 여는 공개 화면의 HTML 에 Studio 청크 셋이 `modulepreload` 로 붙어 있었다 —
|
||||
읽기만 하는 사람이 편집기 번들을 내려받았다.
|
||||
/**
|
||||
* 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}`,
|
||||
);
|
||||
}
|
||||
}
|
||||
|
||||
`resolveDependencies` 는 주입되는 목록을 그대로 받는다. Studio 청크만 빼고 나머지는
|
||||
그대로 둔다 — 공개 라우트의 미리 받기는 그 화면을 빨리 여는 데 실제로 쓰인다.
|
||||
*/
|
||||
modulePreload: {
|
||||
resolveDependencies: (_filename, deps) =>
|
||||
deps.filter((dep) => !dep.includes("route-tech-log-studio")),
|
||||
},
|
||||
rolldownOptions: {
|
||||
output: {
|
||||
manualChunks: routeChunkName,
|
||||
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.
|
||||
manualChunks: (id: string) =>
|
||||
id.includes("vite/preload-helper")
|
||||
? "preload-helper"
|
||||
: routeChunkName(id),
|
||||
},
|
||||
},
|
||||
},
|
||||
},
|
||||
};
|
||||
});
|
||||
|
||||
Reference in New Issue
Block a user