npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

stream-pipeline

v0.0.4

Published

Efficient way of connecting disparate streams

Downloads

68

Readme

pipeline

Efficient way of connecting disparate streams

When you want to connect several disparate pipes in a configuration driven way use this tool. Disparate here means pipes that at the end should buffer completely.

a => b => c wait for c to end then c => d => e wait for e to end then e => f => g

How to.

Create a config and pass it in to pipline.

    var pipeline = new Pipeline(
        [
            { 
                pipes: [
                    through(function(d) {
                      d.newData = 1;//Math.random();
                      this.queue(d);
                      }),
                    JSONStream.stringify(),
                ]
            },
            {
                pipes: [
                    JSONStream.parse(),
                    JSONStream.stringify()
                ]
            },
            {
                pipes: [
                    JSONStream.parse()
                    
                ]
            }
            
        ]
    );

Pipeline exposes the 'in' stream and 'out' stream through two properties.

process.stdout.pipe(pipeline.out);
pipeline.in.write("hello");

The above will break because pipeline.out in the above example is objects. but add in another JSONStream.stringify and you will have a working pipeline.

Pipelines are executed in the array order they are provided.

Please look at the Test file for examples.