webServer.url port does not match expected test URL
webServer.url points at port 3000, while expected test URL points at port 4173.
Playwright webServer preflight
Paste a sanitized Playwright config and the URL your test expects. The checker compares server URL, baseURL, port, timeout, and local/CI reuse behavior without running Playwright or touching your repo.
The pasted Playwright config has likely webServer/baseURL blockers.
webServer.url points at port 3000, while expected test URL points at port 4173.
CI cold starts often need at least 60000ms. Shorter timeouts can create flaky server startup failures.
CI usually starts from a clean machine. Prefer reuseExistingServer: !process.env.CI so local runs can reuse a server but CI starts one.
Playwright webServer/baseURL preflight Status: fail Summary: The pasted Playwright config has likely webServer/baseURL blockers. Parsed config: - webServer detected: yes - command: npm run preview - webServer.url: http://localhost:3000 - use.baseURL: http://localhost:3000 - expected test URL: http://localhost:4173/dashboard - timeout: 30000 - reuseExistingServer: true Findings: - fail: webServer.url port does not match expected test URL - webServer.url points at port 3000, while expected test URL points at port 4173. - warn: webServer.timeout is short - CI cold starts often need at least 60000ms. Shorter timeouts can create flaky server startup failures. - fail: reuseExistingServer is true in CI - CI usually starts from a clean machine. Prefer reuseExistingServer: !process.env.CI so local runs can reuse a server but CI starts one. Checklist: - Make webServer.url and use.baseURL point to the same protocol, host, and port. - Use reuseExistingServer: !process.env.CI for the common local/CI split. - Add an explicit timeout for slow CI server startup. - Run the real Playwright suite after this static preflight.
It checks static Playwright config fields for server URL, baseURL, port, timeout, reuseExistingServer, and local-vs-CI mismatch risk.
It does not run Playwright, start a server, inspect your repository, install dependencies, or prove that a browser test is correct.