-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
remove ip package #94
Conversation
package.json
Outdated
@@ -23,7 +23,7 @@ | |||
"socks5" | |||
], | |||
"engines": { | |||
"node": ">= 10.13.0", | |||
"node": ">= 16.0.0", |
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.
dropping support for node version is a breaking change - it looks like ip-address
v7 supports Node v10; would it be possible to use that instead?
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.
I think i'll just bump the overall package to 3.0.0. Anything prior to node 16.x isn't being maintained at this point.
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.
that'll mean downstream packages will need to explicitly update their dependency on sock
to v3 (and require that they support node v16+) which could delay rollout - any chance of getting a final v2 patch with this before immediately releasing v3?
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.
btw If you're running into problems related to Node 10, I'm happy to have a crack at getting things working :)
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.
I think it may just be the typescript building not working on 10.x, the actual javascript may work fine tbh.
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.
Okay, yeah so it works just fine on plain javascript node 10.24.1 with ip-address 9.x, it's just the building of the typescript/etc won't work for anything less than 16.
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.
So I'll just leave the min version as-is with 10.x, and release as 2.8.0? Or should this just be a bug/patch as 2.7.2?
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.
I think technically it's a feature but I don't think anyone would complain if you released it as a bug fix 🤷
just want to say thanks for the fast response on this ❤️ |
Thank you for sorting this out so quickly, much appreciated! |
I don't think Dependabot opens a fix as it's still used by some dev dependencies, but this change reduces the scope by removing it from the deployed app. Refs JoshGlazebrook/socks#94, indutny/node-ip#150
No description provided.