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

through-pipes

v0.0.4

Published

Create a through stream that wraps/nests a number of pipe statements.

Downloads

3

Readme

through-pipes

Create a through stream that wraps/nests a number of pipe statements.

Install

Install with npm.

npm install --save-dev through-pipes

Usage

The primary use case is where you wish to define a subroutine that is to be used in a pipe statement. However in this subroutine you would also like to pipe through a set of streams.

The following example encapsulates a pre-minify and ugilfy as a minify subroutine for Gulp.

var through = require('through-pipes');
var ngmin = require('gulp-ngmin');
var uglify = require('gulp-uglify');

function minify() {
  return through(function(readable) {
    return readable
      .pipe(ngmin())
      .pipe(uglify())
  }
}

var gulp = require('gulp');

gulp.task('default', function() {
  gulp.src('js/**/*.js')
    .pipe(minify())
    .pipe(gulp.dest('dist'))
});

Note that minification is an arbitrary and somewhat inappropriate example. You would normally be implementing something more specific that would be contained in a separate node package.

Other than the top-level factory method, there are a number of other methods that may be used to push input explicitly to the subroutine.

The following example pushes 3 files, and a stream end event, directly to the readable stream.

var through = require('through-pipes');
var ngmin = require('gulp-ngmin');
var uglify = require('gulp-uglify');

through(function(readable) {
  return readable
    .pipe(ngmin())
    .pipe(uglify())
})
.output(function(file) {
  /* do something with each minified file */
})
.done(function() {
  /* do something at the end */
})
.input(fileA, fileB, fileC)
.end();

Limitations

Suitable for object streams only.

Reference

(method)

Creates a new instance.

@param {function(stream.Readable):stream.Readable} method A factory method that returns a stream

@returns {stream.Through} A through stream that wraps the pipe

.input(...)

Bypass the through stream and directly push values to the internal input stream.

@param {...object} Any number of objects to add to the input.

@returns {stream.Through} The through stream on which the method was called.

.end()

Bypass the through stream and directly push null to the internal input stream to trigger end.

@returns {stream.Through} The through stream on which the method was called.

.output(method)

A convenience for .on('data', method).

@param {function(string, function)} method The method to be called on the data event.

@returns {stream.Through} The through stream on which the method was called.

.done(method)

A convenience for .on('end', method).

@param {function(string, function)} method The method to be called on the end event.

@returns {stream.Through} The through stream on which the method was called.