Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

@googlebot I signed it!

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

Thanks for creating this! One suggestion: as the code for integrating this is trivial, would you mind implementing this directly instead of adding an additional dependency?

@sebastianbenz I searched for this fix that doesn't require any additional libraries.
But that seemed difficult.
If I use node-fetch, you need an agent like HttpProxyAgent, which is also an additional library.
Is there any idea to implement node-fetch agent without using it, implementation without node-fetch, or any other method?

Sorry for not being more clear. Integrating https://www.npmjs.com/package/http-proxy-agent is fine as it seems to be the "standard" node way of integrating of proxy. What I'd like to avoid is integrating node-fetch-with-proxy as it's a super thin wrapper with only a few LOC and super low usage.

@sebastianbenz Sorry for late reaction.
This time https-proxy-agent matches so I added and fixed code.

@sebastianbenz I checked cross-fetch library but it doesn't support agent like node-fetch.

Should I replace cross-fetch to node-fetch? or any ideas?

Hm - that's annoying. I think it's fine to replace cross-fetch in that case and we don't release a browser bundle yet which would benefit from cross fetch.

@sebastianbenz Ok, so let's try replacing "cross-fetch" with "node-fetch" once in a separate branch.
Is it possible to merge this pull request? I'm using next.js now, but I'm having trouble with next.js because it relies on amp-toolbox and I'm having to wait a huge amount of time for postinstall in a proxy environment.