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

pipe-program

v0.0.2

Published

Create a pipe-able program. stdin goes to your function, your function return goes to stdout.

Downloads

1

Readme

pipe-program

Easily create a pipe-able program.

npm install pipe-program --save

yarn add pipe-program

Why

In order to encourage smaller, focused programs, it should be easy to compose programs by using the unix pipe "|" operator. Your program should read from stdin and write to stdout unless it's actually meant to write to the file system or do some other IO.

Ideally your program would just be a function and something else takes care of all the reading and writing from the process.stdin and stdout. The pipe-program package is that "something else".

Simple example

import pipeProgram from 'pipe-program'

function myFunction (stdin) {
  return stdin + ' This is stdout.'
}

export default pipeProgram(myFunction)

// echo -n "This is stdin." | node simple-example.js
// "This is stdin. This is stdout." will be printed.

Async example

import path from 'path'
import pipeProgram from 'pipe-program'
import { readFileAsync } from 'fs-extra-promise'

/**
 * This will read the file passed in through stdin
 */
function myAsyncFunction (stdin) {
  return readFileAsync(path.resolve(__dirname, stdin))
}

export default pipeProgram(myAsyncFunction)

// echo -n "package.json" | node async-example.js
// The contents of package.json (if it exists) will be printed.

Stream example

pipe-program is designed to work with streams. If your function returns one it will be piped to stdout.

import path from 'path'
import { createReadStream } from 'fs'
import pipeProgram from 'pipe-program'

function myStreamFunction (stdin) {
  return createReadStream(path.resolve(__dirname, stdin), {
    encoding: 'utf8'
  })
}

export default pipeProgram(myStreamFunction)

// echo -n "package.json" | node stream-example.js
// The contents of package.json (if it exists) will be printed.

Errors

All errors, both async and sync, will be written to process.stdout. If you return a rejected promise it will attempt to pass the error to stdout.