Skip to content
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 compatibility with Node.js 14 #104

Merged

Conversation

lpinca
Copy link
Contributor

@lpinca lpinca commented May 16, 2020

If the socket is writable, a write is attempted and an
ERR_SOCKET_CLOSED error is emitted because the socket was never
connected.

If the socket is writable, a write is attempted and an
`ERR_SOCKET_CLOSED` error is emitted because the socket was never
connected.

Refs: nodejs/node#32272
@lpinca lpinca force-pushed the fix/compatibility-with-nodejs-14 branch from 122e416 to 450237e Compare May 16, 2020 14:27
Copy link
Collaborator

@BYK BYK left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, @TooTallNate ?

@lpinca
Copy link
Contributor Author

lpinca commented Jun 29, 2020

Friendly ping.

@TooTallNate TooTallNate merged commit c30a9dc into TooTallNate:master Jul 28, 2020
@TooTallNate
Copy link
Owner

Thank you!

@lpinca lpinca deleted the fix/compatibility-with-nodejs-14 branch July 29, 2020 09:16
@lpinca
Copy link
Contributor Author

lpinca commented Oct 29, 2020

@TooTallNate can you please cut a new release?

@jfmartinez
Copy link

Hi! Ran into this while testing, will it be possible to cut a release with this fix?

@TooTallNate
Copy link
Owner

https://github.com/TooTallNate/node-https-proxy-agent/releases/tag/5.0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants