browserify / browserify/labeled-stream-splicer

Wrapping Writable Streams with Readable?

Open
#6 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
42
Forks
5
PR merge metrics
No merged PRs in 30d

Description

Hi there, so I am using this package to create a customizable pipeline if desired in a package. I noticed however, if I add a Writable stream that it gets wrapped with a Readable stream. I understand that decision in the aim that the pipeline is used as the middle between an initial Readable Stream and an ending Writable Stream. However, in my use case the Writable stream is the end and my intention was that if the user wants to change that they could remove that step from the pipeline and replace it with another. What would you suggest in response to that? So far I just have another function that I can pipe the labeled stream splicer pipeline into that produces a writable stream. It is an ok solution, but I would much prefer to have it all in the pipeline and require the user to invoke only a single method to run it.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.