c0b
commented
6 years ago the problem with Heroku's fork (https://github.com/heroku/socksv5) why not keep its issues board open? as we know here this issues board got no response from @mscdex and I am at a situation want to report a new issue, not sure is to report to heroku/socksv5 has better to have a PR and closed sooner?
you see @heroku/socksv5 has advanced to version 0.0.9 would be better to be based off, will it be acceptable if open a new PR to https://github.com/heroku/socksv5 ? ; or will fix on myself at another fork? [not good];
- https://www.npmjs.com/package/socksv5 => 0.0.6
- https://www.npmjs.com/package/@heroku/socksv5 => 0.0.9
from https://github.com/heroku/socksv5/graphs/contributors?from=2017 /cc @jdxcode
update: another issue with heroku is why not change the repo line https://github.com/heroku/socksv5/blob/master/package.json#L26 ??
q2dg
Hi! Is this repository still being maintained? It seems like there are a few breaking issues with newer versions of node, and there haven't been any changes to this repo lately.
From what I can see, Heroku's fork is the most up-to-date, and is also published to npm (
@heroku/socksv5).(I totally understand if this package is in maintenance mode though, and maintaining packages is hard work! Just unsure whether I should look at alternative packages for these issues.)