Combo Draft: Web Deploy Verification

Scenario

"Deploy succeeded" and "the page is really reachable" are two different things. vite-deploy completes the build and publish, but whether the published page really opens and its key elements exist could previously only be verified by a human. This combo chains "build → verify" into a deterministic pipeline: Vite does the build (vite-deploy entry, content-hashed assets), playwright-mcp gives the Agent a browser control surface, and the Agent opens the page to assert key elements and routes. Each tool owns one stage, no overlap.

Combo members

vite-deploy: frontend build (output side, existing entry, actually Vite 5.x)

Download: npm package vite (entry name vite-deploy, official; China npmmirror prefix)
Version: 5.0~5.4 (recorded and measured 5.4.21 on 2026-08-29)
Install:

npm install --save-dev vite --registry=https://registry.npmmirror.com
npx vite build

playwright-mcp: browser verification (verification side, newly recorded)

Download: npm package @playwright/mcp; install-free npx -y @playwright/mcp@latest
Version: >= 0.0.79 (measured 2026-08-29; Node >= 18)
Install:

npm_config_registry=https://registry.npmmirror.com npm install -g @playwright/mcp
npx --no-install playwright install chromium

Install order

vite-deploy (build) → 2. playwright-mcp (verify); the combo is ready only when all are installed and running. playwright-mcp's first run downloads the browser engine (~114MiB).

Dependency warnings

Node >= 18 (both tools npm form); reserve ~114MiB disk (browser engine)
playwright-mcp listens on port 8931 by default (--port can change); use --headless in GUI-less environments
Permission boundary: playwright-mcp's default file access is limited to workspace roots; sensitive switches must be explicitly enabled
Conflicts: the two tools' write surfaces don't overlap (dist/ build output / browser temporary profile) → compatible (combo measured state: 2026-08-29 browser smoke passed)

Acceptance check (one shot)

Run this block after installing; all green = combo ready; any failure -> back to the matching step in the install walkthrough.

npx vite --version
npx --no-install @playwright/mcp --version
npx vite build

预期输出: 5.x; @playwright/mcp 0.0.79+; vite build completes and dist/ appears (5.4.21 build measured 2026-08-29). Browser assertion chain = serve + playwright-mcp opens the page and asserts (chromium downloaded)

Note: member-level measured; headless environments use --headless.

Verification evidence

Every combo is measured in an isolated environment (smoke + write-surface check); unmeasured items are honestly marked in the text, and measurement dates are listed in the verification section below.

Verified 2026-08-29 · TTL expires 2027-02-25 (180 days)

2026-08-29: playwright-mcp 0.0.79 measured (npmmirror 3s install; server started listening on 8931; chromium headless downloaded 113.9MiB + page smoke title=ok); combo-chain measurement see the next line
2026-08-29: vite-deploy entry recorded and measured (npmmirror 7s installed 12 packages, vite 5.4.21 build produced dist/)
2026-08-29 full chain measured PASS: vite 8.2.2 built dist/ → python3 http.server 8977 served the static site → playwright headless opened http://127.0.0.1:8977/ asserting title=ComboLinkOK + #hero=deployed-ok (local repro log 2026-08-29)

Combo Draft: Web Deploy Verification ✓ Verified