Skip to content

Recognize vite strictPort exits as port collisions in claimAndBoot #1662

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
RhysSullivan merged 1 commit into from
Aug 18, 2026
Merged

Recognize vite strictPort exits as port collisions in claimAndBoot #1662

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions e2e/src/ports.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -234,8 +234,14 @@ export const isAddrInUse = (error: unknown): boolean => {
for (let cursor: unknown = error; cursor instanceof Error; cursor = cursor.cause) {
if ((cursor as NodeJS.ErrnoException).code === "EADDRINUSE") return true;
// The emulate/vite boot glue wraps the OS error in a plain Error whose
// message carries the code, so match the text too.
if (/EADDRINUSE/.test(cursor.message)) return true;
// message carries the code, so match the text too. Vite's --strictPort
// exit never says EADDRINUSE at all — the CLI catches the bind failure
// and dies with "Port N is already in use", which reaches us only as
// BootProcessExitError's log tail — so match that phrasing as well, or
// the claimAndBoot re-claim retry never engages for the most common
// collision (a Linux ephemeral outbound socket grabbing the claimed
// port between probe release and vite's bind).
if (/EADDRINUSE|is already in use/.test(cursor.message)) return true;
}
return false;
};
Expand Down
Loading