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

remove ip package #94

Merged
merged 6 commits into from
Feb 12, 2024
Merged

remove ip package #94

merged 6 commits into from
Feb 12, 2024

Conversation

JoshGlazebrook
Copy link
Owner

No description provided.

package.json Outdated
@@ -23,7 +23,7 @@
"socks5"
],
"engines": {
"node": ">= 10.13.0",
"node": ">= 16.0.0",
Copy link

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?

Copy link
Owner Author

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.

Copy link

@G-Rath G-Rath Feb 12, 2024

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?

Copy link

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 :)

Copy link
Owner Author

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.

Copy link
Owner Author

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.

Copy link
Owner Author

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?

Copy link

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 🤷

@G-Rath
Copy link

G-Rath commented Feb 12, 2024

just want to say thanks for the fast response on this ❤️

@JoshGlazebrook JoshGlazebrook merged commit 66b7f73 into master Feb 12, 2024
3 checks passed
@retroburst
Copy link

Thank you for sorting this out so quickly, much appreciated!

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.

3 participants