feat: print port in the logged error message after failed WS connec…

…tion with `EADDRINUSE` (#19212)
vitejs · Feb 4, 2025 · 14027b0 · 14027b0
1 parent 602b373
commit 14027b0
Showing 1 changed file with 6 additions and 4 deletions.
diff --git a/packages/vite/src/node/server/ws.ts b/packages/vite/src/node/server/ws.ts
@@ -258,10 +258,12 @@ export function createWebSocketServer(
       }
       handleUpgrade(req, socket as Socket, head, protocol === 'vite-ping')
     })
-    wsHttpServer.on('error', (e: Error & { code: string }) => {
+    wsHttpServer.on('error', (e: Error & { code: string; port: number }) => {
       if (e.code === 'EADDRINUSE') {
         config.logger.error(
-          colors.red(`WebSocket server error: Port is already in use`),
+          colors.red(
+            `WebSocket server error: Port ${e.port} is already in use`,
+          ),
           { error: e },
         )
       } else {
@@ -301,10 +303,10 @@ export function createWebSocketServer(
     }
   })
 
-  wss.on('error', (e: Error & { code: string }) => {
+  wss.on('error', (e: Error & { code: string; port: number }) => {
     if (e.code === 'EADDRINUSE') {
       config.logger.error(
-        colors.red(`WebSocket server error: Port is already in use`),
+        colors.red(`WebSocket server error: Port ${e.port} is already in use`),
         { error: e },
       )
     } else {