DongHyeonka
3754269118
The public site shipped a Releases page and a footer link to a release, and neither could ever have content: the read path existed, the write path did not. This adds the seven release operations to the contract contribution and the gateway, and a Studio screen that can actually write one. The editor is six markdown fields rather than one, because that is what the contract models and what a release note is — why, what, what a reader notices, what it leaves in the code, how it was verified, what is still open. Publishing is separate from saving: a draft saves in any state, but the public query keys on PUBLISHED alone, so publish is where completeness is demanded. No new CSS. The screen reuses the document editor's field classes and the working-copy list's row classes, so it inherits Studio's spacing and type instead of introducing a second look. The footer previously linked `/releases/0.1.0` — a version that did not exist, so the link 404'd, and one that would have gone stale at 0.2.0 anyway. It now points at the changelog index, which is the only place that knows what the latest release is and which reads correctly when there are none. Route inventory, navigation order, message catalog, manual accessibility evidence, artifact baseline, and the pinned gate-shape digest all move with the new route. The digest was recomputed by first reproducing the previous constant from the previous gates.json, so the computation is known to be the one it was pinned under.
82 lines
3.8 KiB
TypeScript
82 lines
3.8 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/question-page.tsx": "route-tech-log-question",
|
|
"/public/pages/topic-page.tsx": "route-tech-log-topic",
|
|
"/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/releases-page.tsx": "route-tech-log-studio-releases",
|
|
"/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,
|
|
},
|
|
},
|
|
},
|
|
});
|