-
Notifications
You must be signed in to change notification settings - Fork 603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: fix EnvHttpProxyAgent for the Node.js bundle #4064
Conversation
The Dispatcher needs some methods from lib/api for EnvHttpProxyAgent, otherwise it's incomplete.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Can you add a test for it? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Added a test - I didn't use mocks but spin up two servers to try to exercise more paths, in case the mocks hide any real issues in the paths that would be otherwise exercised if used for real. Also I just wrote the test to use them together since nodejs/node#57165 doesn't need them exposed individually. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
This relates to...
Refs: nodejs/node#57165
Rationale
The Dispatcher needs some prototype methods from lib/api for EnvHttpProxyAgent, otherwise it's incomplete, and throws a
TypeError: this[kClient].connect is not a function
whenEnvHttpProxyAgent
is handling requests inside the Node.js bundle.Changes
Make the Dispatcher prototype complete in the Node.js bundle.
Features
Bug Fixes
Breaking Changes and Deprecations
Status