ETIMEDOUT for certain calls on Node 16 about typed-rest-client HOT 5 CLOSED

@mmajcica This definitely could be the problem caused by Node 16, this library is mostly used as a rest client for the Azure DevOps in the-box-tasks and supported to correspond tasks use cases, most of the tasks are running with Node 10, so from our side I can exactly say that this library is correctly working with Node 10. Regarding running it with Node 16, truly speaking I don't know if anybody in the team ever tried running this lib with Node 16. I can exactly say that we couldn't guarantee correct work on this Node version, since such a use case has never been tested.

from typed-rest-client.

@EzzhevNikita we are trying to move to node16 and push our code on Azure Functions v4. Both azure-devops-node-api and typed-rest-client are essential for our code and this is not great news. Any plans to test and support at least node 14?

from typed-rest-client.

I also tried with v14.17.0 but still the same outcome.

from typed-rest-client.

@EzzhevNikita so node10 is still actual but MS is pushing us to get on newr version on the other side, check the Q1 feature line for Azure DevOps agents https://dev.azure.com/mseng/AzureDevOpsRoadmap/_workitems/edit/1888423
Deprecate Node 10 from agent and tasks
https://docs.microsoft.com/en-us/azure/devops/release-notes/features-timeline

Not sure how to proceed anymore :/

from typed-rest-client.

I found the culprit. It has to do with a typo inside the NO_PROXY env var used. Though this solves the issue, I would expect that such a typo would not cause such wired issues. This should be investigated, however not by you, but with nodejs community.

from typed-rest-client.