Consider replacing Axios about node-acme-client HOT 4 CLOSED

Hi,

While replacing axios isn't currently on the roadmap, I'll make sure to keep it in mind for a future major release.

Regarding the error you are experiencing while using jest it seems like this is a common issue with axios. I've implemented a fix for this in 70de66f by explicitly setting Node as the default HTTP adapter, because, as you said, there is no reason for axios to select the browser adapter in this client.

Will publish with v4.0.2 and ping once done.

Thanks!

from node-acme-client.

Great, thanks. I can recommend either make-fetch-happen or my fetch-enhanced for fetch implementations that support automatic http proxy discovery which is a quite important feature in enterprise environments (Thought I guess in most cases, a application that does ACME challenges will have some form of direct internet connectivity).

from node-acme-client.

Fix published with v4.0.2!

from node-acme-client.

Maybe you want to consider using undici.fetch. It's also available as (experimental) global fetch starting with Node.js 18.

from node-acme-client.