Skip to content
This repository has been archived by the owner on May 5, 2023. It is now read-only.

Update http-proxy-agent and https-proxy-agent deps #16

Closed
ChALkeR opened this issue Mar 5, 2018 · 4 comments
Closed

Update http-proxy-agent and https-proxy-agent deps #16

ChALkeR opened this issue Mar 5, 2018 · 4 comments

Comments

@ChALkeR
Copy link

ChALkeR commented Mar 5, 2018

Those are outdated atm and use old Buffer API, which is going to start printing runtime warnings on Node.js 10.0.

Tracking: nodejs/node#19079
@ChALkeR ChALkeR mentioned this issue Mar 5, 2018
Closed
@shibukawa
Copy link

And security issues exist:

@ChALkeR
Copy link
Author

ChALkeR commented Apr 11, 2018

@shibukawa That was the primary reason for opening this issue here.

@ChALkeR
Copy link
Author

ChALkeR commented Apr 11, 2018

@TooTallNate Thanks!

@shibukawa
Copy link

@TooTallNate Thank you for your quick response!

FedeCanet added a commit to FedeCanet/node-pac-proxy-agent that referenced this issue Apr 23, 2019
@FedeCanet
Too tall nate master (#3)
dbff3e6 
* Upgrade pac-resolver

* update "mocha" to v3.4.2

* remove older versions from Travis

* drop Node < 1 support, test v6, v7 and v8

* fix judo

* Release 1.1.0

* update dependencies

* add 'use strict'

* use `Object.assign()`

Removes the `extends` dependency

* drop Node 1, 2 and 3 from Travis-CI

* update "socks-proxy-agent" to v3

* Release 2.0.0

* Update dependencies

Closes TooTallNate#16.

* Test Node.js v9

* 2.0.1

* Revert changes that breaks node 4.0

Socks-proxy-agent breaks node 4.0 by introducing ES6 syntax

* Update dependencies

* Don't test Node.js v4 and v5

* 3.0.0
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ChALkeR @shibukawa