Update request agent-base

[seiya-git]

Please update agent-base dependency in package.json
ref: TooTallNate/node-agent-base#35

[seiya-git]

@TooTallNate ping?

[JasonZigelbaum]

@TooTallNate is it possible to get an update on this? It's causing issues for anyone using this package (or a package using this package) with the same severity as: TooTallNate/node-agent-base#35. Thanks!

[ghost]

We very much need this updated so we can get around TooTallNate/node-agent-base#35

[artem-karpenko]

Need this very much, in particular this makes got requests fail when node-proxy-agent is indirectly required. Any update, @TooTallNate?

[magicdawn]

ping @TooTallNate again, +1 on got proxy issues.

[boisei0]

Additonally, when updating please release this as minor release rather than a major like happened with agent-base itself. Any attempts at using got in integrations in other projects that might have other integrations depending somewhere on any of the proxy-agents, makes it impossible to use https URLs because of the patching in v4 of agent-base.
another ping for @TooTallNate

[apexad]

Need this too!
Please @TooTallNate

[vnenkpet]

Google Cloud suddenly probably changed its nodejs10 runtime and this became an issue for us using got. I can't find a proper solution for this.

[santiago-perez-axa]

I also got the same problem with got versions >=10

[vnenkpet]

Just a tip for anyone who needs to solve this - try running npm ls agent-node and see which dependencies require the old version. For me it was the mailgun-js package so I fixed my problem by removing it and implementing Mailgun API client myself.

[fishsaidno]

+1

└─┬ [email protected]
  └─┬ [email protected]
    ├── [email protected]           <---
    ├─┬ [email protected]
    │ └── [email protected]         <---
    ├─┬ [email protected]
    │ └── [email protected]         <---
    ├─┬ [email protected]
    │ └── [email protected]         <---
    └─┬ [email protected]
      └── [email protected]         <---

[alvis]

ping @TooTallNate
Sorry to bother, but the outdated dependency on socks-proxy-agent is causing problems on us.