Recently discovered an Issue where if the local development page is open in the browser, still attempting to connect via live-reload to the local development server, it will cause the command line process to fail or timeout.
localhosttab still open…
λ npm start > gatsby develop -o > Running Dev Command “gatsby develop --port $PORT” > Ready! Available at http://localhost:3000 Error: socket hang up at connResetException (node:internal/errors:683:14) at Socket.socketOnEnd (node:_http_client:471:23) at Socket.emit (node:events:406:35) at Socket.emit (node:domain:470:12) at endReadableNT (node:internal/streams/readable:1329:12) at processTicksAndRejections (node:internal/process/task_queues:83:21)
Haven’t figured out exactly why, but whenever I am getting the following error when trying to boot my local development server it’s quickly resolved by closing the
localhost:3000 browser tab.