Mark
96fa8e8e11
Task 1 of Plan 01-11 (Puppeteer UAT harness). - npm install --save-dev puppeteer@^25.0.2 tsx@^4 @types/node resolved: puppeteer@25.x, tsx@4.22.1, @types/node@25.8.0 pulls ~150MB Chromium binary at install time (T-1-11-03 — accepted, package-lock pins resolved hashes via @puppeteer/browsers). - package.json scripts: add build:test + test:uat (per RESEARCH §10 two-bundle orchestration); existing dev/build/preview/test untouched. - vite.test.config.ts: extends ./vite.config.ts via mergeConfig with mode:'test' + build.outDir:'dist-test' + emptyOutDir:true. Verified npm run build:test produces dist-test/ in 7.93s; npm run build keeps producing dist/ in 7.67s (no clobber). - tsconfig.json `include: ["src"]` already covers src/test-hooks/**/* via wildcard — no edit needed. - tests/background/no-test-hooks-in-prod-bundle.test.ts: Tier-1 gate mirroring sw-bundle-import.test.ts's execFile pattern. Greps the BUILT dist/ tree for 5 forbidden hook surfaces (one `it` per surface for granular failure isolation): __mokoshTest, simulateUserStop, getSegmentCount, setCurrentStream, setSegmentCountGetter. All 5 surfaces absent today (RED-then-GREEN polarity inverted — the gate is GREEN now and MUST stay GREEN after Task 2 lands the hooks). SKIP_BUILD=1 escape hatch for developer iteration. - .gitignore: add dist-test/ (no point versioning generated test bundle). Verification: - npx tsc --noEmit: exit 0 - npm run build: exit 0; dist/ populated (375.37 kB SW chunk) - npm run build:test: exit 0; dist-test/ populated (identical chunk sizes — the gated dynamic imports do not land until Task 2; this commit only proves the two-bundle plumbing) - SKIP_BUILD=1 npx vitest run tests/background/no-test-hooks-in-prod-bundle.test.ts: 6/6 GREEN (1 build-sanity + 5 forbidden-surface) - SKIP_BUILD=1 npx vitest run (full suite): 89/89 GREEN (83 baseline + 6 new Tier-1 surfaces = 89) Working-tree cleanup: a stale 5.4 MB tests/fixtures/last_30sec.webm (unrelated operator smoke regen present at session spawn) was stashed before running the baseline — it caused the webm-playback test to time out at 5s. After stashing back to HEAD's 1.9 MB fixture, baseline passes cleanly. Not committing the fixture restoration here (pre-existing working-tree state, not part of Task 1). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
32 lines
857 B
JSON
32 lines
857 B
JSON
{
|
|
"name": "ai-call-extension",
|
|
"version": "1.0.0",
|
|
"description": "Browser extension for recording operator sessions",
|
|
"type": "module",
|
|
"scripts": {
|
|
"dev": "vite",
|
|
"build": "tsc && vite build",
|
|
"build:test": "tsc && vite build --mode test --config vite.test.config.ts",
|
|
"preview": "vite preview",
|
|
"test": "vitest run",
|
|
"test:uat": "npm run build:test && tsx tests/uat/harness.test.ts"
|
|
},
|
|
"dependencies": {
|
|
"jszip": "^3.10.1",
|
|
"rrweb": "^2.0.0-alpha.4",
|
|
"ts-ebml": "^3.0.2",
|
|
"webm-muxer": "^5.1.4"
|
|
},
|
|
"devDependencies": {
|
|
"@crxjs/vite-plugin": "^2.0.0-beta.25",
|
|
"@types/chrome": "^0.0.268",
|
|
"@types/node": "^25.8.0",
|
|
"puppeteer": "^25.0.2",
|
|
"tsx": "^4.22.1",
|
|
"typescript": "^5.5.4",
|
|
"vite": "^5.4.2",
|
|
"vite-plugin-node-polyfills": "^0.27.0",
|
|
"vitest": "^4"
|
|
}
|
|
}
|