Provide streams as separate modules

I really like the tools that this project brings to node streams, but I would be anxious to include ALL of the functionality at once when using this client-side. Would it make sense to split all these streams into separate modules so that once could have fine-grained control over what they want?

The issue names no files, tests, or entry points. Start by reviewing how the existing streams are organized and how the browser/client build is produced; determine module boundaries and verify that consumers can load selected streams without changing current behavior.

Written by the indexing model from the issue text.