-
Notifications
You must be signed in to change notification settings - Fork 1
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
Does it support readable-stream / 0.10 #2
Comments
Are you saying there are problems with those streams or just suggesting to try them out ? I was planning to revisit this work once new streams land to node. |
If you're willing to submit tests cases against either one I'm happy to take those ;) |
I havn't tried, but I was just thinking about whether I should use |
If this new streams are as backwards compatible as izs claims them to be, then there are no reasons why this won't work. As I said I'm more then happy to make this work with those streams if it isn't a case already, but please submit a test case that is broken so I can fix it. At the moment test run against |
I will look into it at some point :D |
Just write whatever you was planing to and point it out if it does not works. Would be great to have tests even if it works though. |
Doesn't work on Even if you did Fix method so it doesn't run into dedup issues. |
You can not solve problem by changing |
As of the issue you've pointed out I don't think that is an issue since So it's probably something else, maybe a dedup issue indeed. Good rule of thumb for has being putting |
I'll write a test that would use this ReadStream to make sure it works and will attempt to fix if it doesn't. |
Try reducing
Raynos/read-stream
orisaacs/readable-stream
The text was updated successfully, but these errors were encountered: