silverwind
silverwind
As per https://github.com/nodejs/node/issues/8381, the following environments support these variables by default: - Python - Go - Ruby - R curl and wget also use them by default and I'm sure...
Possibly, but first I want to create the parser for the env vars. I have a WIP repo for that, will update here once it's in a usable state. I...
Just adding another data point, [bun](https://bun.sh/blog/bun-v0.5.0#support-for-https-proxy) also now supports these variables out of the box.
Is it okay to cache `ProxyAgent`s for each environment variable in-memory? We shouldn't instantiate new agents every request, and I was thinking of doing a LRU cache that holds the...
Actually, thinking again, if we have a agent cache like ````js { "https://proxy1:3128": ProxyAgent, "https://proxy2:3128": ProxyAgent, } ```` It should not be neccessary to clear this cache ever because even...
Yeah, in a general use case, there would only be two cache entries, one for HTTP and one for HTTPS. If a user wants more dynamic behaviour, they can just...
I'll unassign myself for now, I can't find the motivation to complete this, and I don't want to block anyone else from working in it.
@KhafraDev invited you to my private repo for the env parsing. It's really not much so you could instead just fresh-start with the env parsing based on `proxy-from-env`. The tasks...
This is bound to cause issues because it both changes the identify of `globalThis.fetch` as well as `globalThis.fetch.toSource()`. I strongly recommend against this monkey-patching and I would probably avoid using...