-
Notifications
You must be signed in to change notification settings - Fork 344
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
DO NOT USE THIS THING #120
Comments
If you have already written code against |
whoa, lost a few hours trying to figure out why it was not working for my use case, and it really looked like it wasn't consuming my stream properly. thanks for the reminder :) |
Fantastic! I've spent almost a day to find the problem in my code, but the problem was in that lib. |
@mmontag thank you so much for this thread. I did spent hours with issues with this package and unzipper did work as a drop-in replacement without any issues inside modern async code! |
Wooh. Thanks! |
Wow, thanks for this issue. I've been tracing weird file behavior for hours. Couldn't figure out why intermittently I couldn't overwrite a file that had been unzipped. Following this post I think it couldn't overwrite the file because it's file handle was probably still in use. Thanks a ton @mmontag |
Thanks, @mmontag! After spending a day writing code that uses this it's fantastic to have a drop-in replacement. |
@EvanOxfeld I hope you are alive. Could you please mark this package as deprecated? It will help to make NodeJS ecosystem less cluttered. |
Just a warning to amplify the sentiments of others here and on StackOverflow.
See https://stackoverflow.com/a/46967462/264970
The text was updated successfully, but these errors were encountered: