fix(dev): dev release manifest를 src 밖에 쓰고 Vitest에서는 만들지 않는다
문제 c15345c의 플러그인은 apply: "serve"라 Vitest가 Vite를 띄울 때도 돌아, test:unit마다 자식 프로세스로 manifest를 쓴다. 출력 위치 src/.generated/dev-release-manifest.json에는 자리표시자의 routeChunks(샘플 경로)가 들어 있다. test:sample-removal의 잔여 검사는 src/를 훑으므로 FE-GATE-020이 "fixture-id-residue: src/.generated/dev-release-manifest.json"으로 실패한다. 고른 방법 - 출력을 빌드의 contract set 생성물 옆 .generated/frontend-runtime/로 옮긴다 (무시 대상). - apply가 serve이면서 VITEST가 없을 때만 돈다. 테스트는 서버에서 manifest를 받지 않는다. 검증 - browser-files capability spec(dev server) chromium 3건 통과, 생성물이 새 위치에 생긴다. - test:unit 2,880건 통과, 실행 뒤 src/.generated에 manifest가 없다. Refs: docs/reviews/2026-11-03-maturity-review/README.md 14.6 X2 #3
This commit is contained in:
@@ -4,8 +4,12 @@ import path from "node:path";
|
||||
|
||||
import type { Plugin } from "vite";
|
||||
|
||||
/** Generated at dev server start; ignored with the rest of src/.generated/. */
|
||||
export const DEV_RELEASE_MANIFEST_PATH = "src/.generated/dev-release-manifest.json";
|
||||
/**
|
||||
* Generated at dev server start, beside the build's generated contract set and
|
||||
* ignored with it. Not under src/: the removal drills scan src/ for the
|
||||
* sample's names, and this copies the placeholder's route chunks.
|
||||
*/
|
||||
export const DEV_RELEASE_MANIFEST_PATH = ".generated/frontend-runtime/dev-release-manifest.json";
|
||||
|
||||
/**
|
||||
* Serve only. The dev server answers the runtime's release-manifest request
|
||||
@@ -19,7 +23,9 @@ export const DEV_RELEASE_MANIFEST_PATH = "src/.generated/dev-release-manifest.js
|
||||
export function devReleaseManifestPlugin(repositoryRoot = process.cwd()): Plugin {
|
||||
return {
|
||||
name: "frontend-dev-release-manifest",
|
||||
apply: "serve",
|
||||
// Vitest also starts Vite in serve mode; tests never fetch the manifest
|
||||
// from a server, so they skip the child process.
|
||||
apply: (_config, env) => env.command === "serve" && !process.env["VITEST"],
|
||||
configureServer(server) {
|
||||
execFileSync(
|
||||
process.execPath,
|
||||
|
||||
@@ -10,7 +10,7 @@ import { DEV_RELEASE_MANIFEST_PATH } from "./lib/dev-release-manifest.ts";
|
||||
* installed now. Boot checks that set against the installed declarations, so
|
||||
* a placeholder with a fixed set refused every app with one more feature
|
||||
* (CONTRACT_SET_PACKAGE_MISSING) until someone edited it by hand. The output
|
||||
* is generated and ignored, as src/.generated/ is.
|
||||
* is generated and ignored, as .generated/ is.
|
||||
*/
|
||||
export async function writeDevReleaseManifest(
|
||||
source = "public/release-manifest.json",
|
||||
|
||||
Reference in New Issue
Block a user