Resolving ETIMEDOUT Errors in Vite during Local Development

[neel-raval]

Hello everyone,

I'm currently encountering persistent ETIMEDOUT errors when trying to run my Vite development server. This issue occurs intermittently but frequently enough to disrupt the development process. The error seems related to Vite's network operations or possibly file system access limitations.

Error Details:

Error: ETIMEDOUT: connection timed out, read
Emitted 'error' event on ReadStream instance at:
at emitErrorNT (node:internal/streams/destroy:169:8)
at emitErrorCloseNT (node:internal/streams/destroy:128:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -60,
code: 'ETIMEDOUT',
syscall: 'read'
}

Steps Taken:

• Checked and ensured stable internet connection.
• Configured Vite to run on different ports to avoid potential conflicts.
• Cleared node_modules and reinstalled all dependencies.
• Tried running Vite with minimal plugins and configurations.
• Checked system logs for any related errors, with no significant findings.

System Configuration:

• OS: macOS
• Node.js version: v20.12.2
• Vite version: v5.2.11

I am looking for any advice, particularly from those who might have faced and resolved similar issues in Vite or related development environments. Insights into potential configuration changes, system settings adjustments, or even debugging techniques would be greatly appreciated.

Thank you in advance for your help and looking forward to your suggestions!

[ArnaudBarre]

Hi!

That's a strange issue and I'm surprised of it given the very standard setup (macOS, recent node & Vite version).

Vite doesn't need an internet connection to work, so there is probably an issue with an access to another ressource. You need to find a way to debug which system call triggered this timeout, I'm surprised that don't have more things on the stacktrace. Does this error crash the server or just add noise to the logs?

[neel-raval]

Hi,

Thank you for your message! The issue was indeed OS-related and has been resolved. Apologies for the late response.

[aiakobou]

Hi, would you elaborate how the problem was solved? OS Update? Which macOS Version did you use?
Thanks!