I have slow Internet connection and when a domain with multiple ip appears, I always get ETIMEDOUT because the connection can not be established in default autoSelectFamilyAttemptTimeoutDefault=250ms. There are a lot of npm packages that use node:net, and it'not possible to wait until all of them implement a mechanism to deal with autoSelectFamilyAttemptTimeout.
What is the feature you are proposing to solve the problem?
I believe it should be fixed by setting autoSelectFamilyAttemptTimeoutDefault in NODE_OPTIONS
What alternatives have you considered?
Now, it's possible to change this parameter by calling net.setDefaultAutoSelectFamilyAttemptTimeout, but I can call it only in my own code, but not from other applications (e.g. yarn), so it won't help in most cases.
Alternatively, you can just increase the default parameter, but it is not flexible solution.
What is the problem this feature will solve?
I have slow Internet connection and when a domain with multiple ip appears, I always get ETIMEDOUT because the connection can not be established in default
autoSelectFamilyAttemptTimeoutDefault=250ms
. There are a lot of npm packages that use node:net, and it'not possible to wait until all of them implement a mechanism to deal withautoSelectFamilyAttemptTimeout
.What is the feature you are proposing to solve the problem?
I believe it should be fixed by setting
autoSelectFamilyAttemptTimeoutDefault
inNODE_OPTIONS
What alternatives have you considered?
Now, it's possible to change this parameter by calling
net.setDefaultAutoSelectFamilyAttemptTimeout
, but I can call it only in my own code, but not from other applications (e.g. yarn), so it won't help in most cases. Alternatively, you can just increase the default parameter, but it is not flexible solution.