You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using node-archiver quite happily but while doing my periodical dependency update procedure, I came across a transient dependency to [email protected] which is quite outdated as v4 has been out for quite some time.
This package quite justly depends on readable-stream@4 but also depends on lazystream@1 which is the one that brings in the outdated dependency to [email protected]
An issue already exists on the lazystream project (jpommerening/node-lazystream#7) but it seems that the project has been dormant for quite some time without any progress on an eventual transfer to a new home (jpommerening/node-lazystream#3 (comment))
Do you think it would be feasible to remove the dependency to lazystream by replacing it by something else, or integrating the functionality directly?
The text was updated successfully, but these errors were encountered:
Hello,
I'm using
node-archiver
quite happily but while doing my periodical dependency update procedure, I came across a transient dependency to[email protected]
which is quite outdated as v4 has been out for quite some time.This package quite justly depends on
readable-stream@4
but also depends onlazystream@1
which is the one that brings in the outdated dependency to[email protected]
An issue already exists on the lazystream project (jpommerening/node-lazystream#7) but it seems that the project has been dormant for quite some time without any progress on an eventual transfer to a new home (jpommerening/node-lazystream#3 (comment))
Do you think it would be feasible to remove the dependency to
lazystream
by replacing it by something else, or integrating the functionality directly?The text was updated successfully, but these errors were encountered: