typescript-build-dist-stale-guard
Root cause: dist/ was committed and served via npx serve dist, but the redesign merged only into src/ — nobody rebuilt/committed dist/, so users got a build that was 2 days behind source. Fix: rebuild, commit dist/, and add a guard that makes staleness fail loudly, plus ignore tooling caches so they never pollute status.
1. Rebuild and commit dist (the immediate fix):
cd ~/game
npm run build # tsc -> dist/
git add dist/
git commit -m "build: rebuild dist to ship neon redesign (was 2 days stale)"
2. Add the verify:dist guard — npm run build && test -z git status dist/ (spec form) implemented as proper POSIX: rebuild, then assert git sees zero changes under dist/:
// package.json
"scripts": {
"build": "tsc -p tsconfig.json",
"verify:dist": "npm run build && test -z \"$(git status --porcelain dist/)\" && echo 'OK: dist/ is in sync with source'",
"serve": "npx serve dist"
}
Cross-platform note: test -z is POSIX; on Windows cmd this needs a Node shim (node -e "process.exit(require('child_process').execSync('git status --porcelain dist/').toString().trim()?1:0)"). CI runs the shell form.
3. Ignore tooling caches — inline # comments are not supported in .gitignore (they silently corrupt the pattern — I hit this live), so comments go on their own lines:
# --- Tooling caches (never commit these) ---
# .vfs: VS Code Remote / Virtual File System cache
.vfs/
.cache/
.DS_Store
# --- Dependencies ---
node_modules/
Reproduced in a real repo at `~/game` (4-commit history: baseline → stale redesign → rebuild dist → gitignore): | # | Test | Result | |---|------|--------| | 1 | Incident reproduced: `dist/index.js` served `"Space Shooter 1.0"` while `src` had the 2.0 redesign; `src` commit 2 days newer than last `dist/` commit | observed | | 2 | `npm run verify:dist` on stale tree exits **1** (catches the incident) | pass | | 3 | Rebuild → `dist/index.js` contains `"Space Shooter 2.0 — Neon Redesign"`; `verify:dist` exits 0 | pass | | 4 | `.vfs/` and `.cache/` created → `git status` still clean, `git check-ignore` matches | pass | | 5 | Untracked stray file added to `dist/` → guard exits 1 | pass | | 6 | Fresh-checkout sim (`rm -rf dist`): guard builds first, self-heals, exits 0 | pass | | 7 | Idempotency: `verify:dist` twice in a row, both exit 0 | pass | | 8 | Deleting a *regenerable* committed dist file: guard rebuilds it → passes (self-healing by design) | documented | | 9 | Deleting a *source* file: tsc doesn't clean `outDir`, so orphaned dist artifacts are invisible to this guard — limitation; hardening is `rm -rf dist && tsc` (clean build) | documented | | 10 | Served game (`node dist/index.js`) prints `== Space Shooter 2.0 — Neon Redesign ==`; final `git status --porcelain` clean | pass | **Real edge case caught while testing:** the first `.gitignore` used inline comments (`.vfs/ # comment`), which git parses as part of the pattern — `.vfs/` was *not* ignored until comments were moved to their own lines.
{"model": "deepseek-v4-flash", "problem_class": "typescript-build-dist-stale-guard", "result": "passed", "tests": 10}Root cause: dist/ was committed and served via npx serve dist, but the redesign merged only into src/ — nobody rebuilt/committed dist/, so users got a build that was 2 days behind source. Fix: rebuild, commit dist/, and add a guard that makes staleness fail loudly, plus ignore tooling caches so they never pollute status.
1. Rebuild and commit dist (the immediate fix):
cd ~/game
npm run build # tsc -> dist/
git add dist/
git commit -m "build: rebuild dist to ship neon redesign (was 2 days stale)"
2. Add the verify:dist guard — npm run build && test -z git status dist/ (spec form) implemented as proper POSIX: rebuild, then assert git sees zero changes under dist/:
// package.json
"scripts": {
"build": "tsc -p tsconfig.json",
"verify:dist": "npm run build && test -z \"$(git status --porcelain dist/)\" && echo 'OK: dist/ is in sync with source'",
"serve": "npx serve dist"
}
Cross-platform note: test -z is POSIX; on Windows cmd this needs a Node shim (node -e "process.exit(require('child_process').execSync('git status --porcelain dist/').toString().trim()?1:0)"). CI runs the shell form.
3. Ignore tooling caches — inline # comments are not supported in .gitignore (they silently corrupt the pattern — I hit this live), so comments go on their own lines:
# --- Tooling caches (never commit these) ---
# .vfs: VS Code Remote / Virtual File System cache
.vfs/
.cache/
.DS_Store
# --- Dependencies ---
node_modules/
Reproduced in a real repo at `~/game` (4-commit history: baseline → stale redesign → rebuild dist → gitignore): | # | Test | Result | |---|------|--------| | 1 | Incident reproduced: `dist/index.js` served `"Space Shooter 1.0"` while `src` had the 2.0 redesign; `src` commit 2 days newer than last `dist/` commit | observed | | 2 | `npm run verify:dist` on stale tree exits **1** (catches the incident) | pass | | 3 | Rebuild → `dist/index.js` contains `"Space Shooter 2.0 — Neon Redesign"`; `verify:dist` exits 0 | pass | | 4 | `.vfs/` and `.cache/` created → `git status` still clean, `git check-ignore` matches | pass | | 5 | Untracked stray file added to `dist/` → guard exits 1 | pass | | 6 | Fresh-checkout sim (`rm -rf dist`): guard builds first, self-heals, exits 0 | pass | | 7 | Idempotency: `verify:dist` twice in a row, both exit 0 | pass | | 8 | Deleting a *regenerable* committed dist file: guard rebuilds it → passes (self-healing by design) | documented | | 9 | Deleting a *source* file: tsc doesn't clean `outDir`, so orphaned dist artifacts are invisible to this guard — limitation; hardening is `rm -rf dist && tsc` (clean build) | documented | | 10 | Served game (`node dist/index.js`) prints `== Space Shooter 2.0 — Neon Redesign ==`; final `git status --porcelain` clean | pass | **Real edge case caught while testing:** the first `.gitignore` used inline comments (`.vfs/ # comment`), which git parses as part of the pattern — `.vfs/` was *not* ignored until comments were moved to their own lines.
{"model": "deepseek-v4-flash", "problem_class": "typescript-build-dist-stale-guard", "result": "passed", "tests": 10}