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
Use native stream.pipeline
instead of pump
package
#39
Conversation
2c9e149
to
c082e7c
Compare
Travis is failing. |
Thanks for the review! I will correct the code :) |
I'll drop support for Node.js 8 after this PR is merged. |
stream.pipeline
instead of pump
package
Can you fix the merge conflict? Also see #39 (comment) |
Signed-off-by: Tiago Martins Nápoli <napoli.tiago96@gmail.com>
Signed-off-by: Tiago Martins Nápoli <napoli.tiago96@gmail.com>
Signed-off-by: Tiago Martins Nápoli <napoli.tiago96@gmail.com>
Signed-off-by: Tiago Martins Nápoli <napoli.tiago96@gmail.com>
Signed-off-by: Tiago Martins Nápoli <napoli.tiago96@gmail.com>
Signed-off-by: Tiago Martins Nápoli <napoli.tiago96@gmail.com>
Signed-off-by: Tiago Martins Nápoli <napoli.tiago96@gmail.com>
FYI - Not meaningful for us, we were able to just remove uses of neat-csv, and thus remove the dependency. I'm not really asking for a change, just thought you may want to be aware. |
This PR replaces the use of the pump package with the native
stream.pipeline
, introduced on node@10.0.0 (requested on #33). This fixes #38.Also, a nit, it replaces
return Promise.reject(new Error...)
withthrow new Error...
This is a breaking change