You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
unfortunately native fetch doesn't support proxy agent because it follow the original implementation from web browsers 😟
my question is, why not bundle node-fetch inside ccxt and avoid using an incomplete fallback? Or at least I think it should be added in the documentation?
The text was updated successfully, but these errors were encountered:
edit: ah, I think I misunderstood. so, you use the bundle in backend, right? hm, seems a valid point, if fallback is used. we will look into this and post an update.
can you please mention exactly which bunder do you use or even it would be nice if you share a simplified project (with tsconfig/package.json) so we would use the same bundling process to reproduce the problem.
Operating System
All
Programming Languages
JavaScript
CCXT Version
Latest
Description
Currently if
ccxt
doesn't findnode-fetch
it use nativefetch
as a fallback here: https://github.com/ccxt/ccxt/blob/master/ts/src/base/Exchange.ts#L1166unfortunately native
fetch
doesn't support proxy agent because it follow the original implementation from web browsers 😟my question is, why not bundle
node-fetch
insideccxt
and avoid using an incomplete fallback? Or at least I think it should be added in the documentation?The text was updated successfully, but these errors were encountered: