update to a maintained through?

[ljharb]

Hi! You depend on through, an excellent package that unfortunately has not been maintained since 2018. I've forked it as https://npmjs.com/@ljharb/through so that I can maintain it (with @dominictarr's blessing), and am using it in https://npmjs.com/tape.

Would you be interested in a PR that switches this project to using my fork instead of the original? It's effectively identical, but it'd ensure any vulnerabilities will be addressed in the future.

[regular]

Oh, hi, thanks for taking care of these classic modules that I still find very relevant today! (I hope someone would take over maintenance of substack's trumpet ...). Just one question: if you have @dominictarr 's blessing, why not simply transfer ownership of the original through repo and module? Going through all dependents to ask to switch over to the scoped version must be tedious and adding one more tree to the forest of modules increases confusion and takes up everyone's time when being forced to research what flavor of through is the maintained one nowadays.

[ljharb]

Because unfortunately he disclaimed ownership and no longer has access to them.

[ljharb]

Filed #40

[valadaptive]

Just to clarify: the codebases are (as far as I can tell) effectively identical at this time, except for the fact that through has 0 dependencies whereas @ljharb/through has 12 nested dependencies for the purpose of Node 0.4 support. You can decide for yourself whether the extra dependencies are worth the Node 0.4 support, but I think it is important to be transparent.