[Question] Error: Timed out waiting 60000ms from config.webServer.
See original GitHub issueI have playwright.config.ts as following with SvelteKit:
import type { PlaywrightTestConfig } from '@playwright/test';
const config: PlaywrightTestConfig = {
fullyParallel: true,
webServer: {
command: 'npm run build && npm run preview',
port: 4173
}
};
export default config;
I got an error Error: Timed out waiting 60000ms from config.webServer.
, so I set timeout
with different values, but I keep getting the same error.
I tried globalTimeout
but the it returns the same error.
How to solve this error?

Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Full Migration Error: Timed out after 60000 ms while waiting to ...
Solution · Check whether the destination database is running properly. · Check whether packet loss or retransmission occurs on the network between ...
Read more >playwright is supposed to start the node server before it tests ...
When I run tests with this code in playwright.config.ts (and no other server running), I get the following error (inconsistently--sometimes ...
Read more >Timed out after 30000 ms while waiting for a server that ...
If yes, then this is a typical timeout error that is shared across all official drivers, where it tries to connect to the...
Read more >Advanced: configuration | Playwright - CukeTest
This file will be required and run after all the tests. It must export a single function. globalTimeout: number - Total timeout in...
Read more >Apache Kafka is not available message is displayed in the ...
ZooKeeperClientTimeoutException: Timed out waiting for connection while in ... show messages ( sames messages than for Problem #2 ) like the following:
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Apparently your server doesn’t start or listens to a different port (not 4173). What does
npm run build && npm run preview
do, can you share the code?We need more information to act on this report. Please file a new one and link to this issue when you get back to it!