How to Fix "TypeErrorhttpsProxyAgent is not a constructor" Warning in Existing Workflows Using Pipedream Proxy?

1

This topic was automatically generated from Slack. You can find the original thread here.

Urgent, in existing workflows we get this warning: TypeErrorhttpsProxyAgent is not a constructor. We use proxy arranged by pipedream about two years ago. What to do?

2

Hi , unfortunately Pipedream engineer will online in a few hours. If you’re in business tier, you should be added to a dedicated support channel. Otherwise, could you send an email to support@pipedream.com stating your account information, workflow url, and your problem?

3

thanks Leo

4

Hi Thijs,

Pipedream will automatically update your NPM packages to the latest version on new workflow deploys.

This error is from a change in the underlying library, you can either pin the NPM version of the HTTP proxy npm package to the last working version, or you can make an update to the import statement as described here: