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
It seems like the only reason undici is our dependency is to support proxy env variables. Direct support for these env variables (NO_PROXY, HTTP_PROXY...) has been implemented in undici in nodejs/undici#2994 and released in version v6.14.0 (nodejs/undici#3147). undici has been updated to version beyond 6.14.0 in Node.js v22.3.0 (nodejs/node#53379). So, once minimum supported Node.js version is 22.3.0, we can remove all custom proxy logic and rely on global fetch entirely.
In the meantime, we could drop custom proxy logic and proxy-from-env dependency, provided that we DON'T use global fetch -but the one imported from undici, which is >6.14.0.
The text was updated successfully, but these errors were encountered:
It seems like the only reason undici is our dependency is to support proxy env variables. Direct support for these env variables (NO_PROXY, HTTP_PROXY...) has been implemented in undici in nodejs/undici#2994 and released in version v6.14.0 (nodejs/undici#3147). undici has been updated to version beyond 6.14.0 in Node.js v22.3.0 (nodejs/node#53379). So, once minimum supported Node.js version is 22.3.0, we can remove all custom proxy logic and rely on global fetch entirely.
In the meantime, we could drop custom proxy logic and proxy-from-env dependency, provided that we DON'T use global fetch -but the one imported from undici, which is >6.14.0.
The text was updated successfully, but these errors were encountered: