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 🙏

© 2026 – Pkg Stats / Ryan Hefner

onstdin

v1.0.0

Published

Calls back on chuncks read via the standard input (stdin). (Synchroneously but non blocking)

Downloads

107

Readme

onstdin

Calls back on chuncks read via the standard input (stdin). (Synchroneously but non blocking)

Installation

$ npm install onstdin

Usage

Example : Create two scripts : myScript.mjs and myOtherScript.mjs

// myScript.mjs

const options = { param1:'hello', param2:'world' }

console.log(JSON.stringify(options,null,2))
// myOtherScript.mjs

import { onstdin } from "onstdin";

onstdin((content) => {
	if(content) {
		const { param1, param2 } = JSON.parse(content ? content : "{}");
		console.log(`${param1} ${param2} onstdin`);
	} else {
		console.log("BOOM !");
	}
});

Execute a pipline via a node commande

$ node ./myScript.mjs | ./myOtherScript.mjs

Output

> hello world onstdin

Complience

When nothing is passed through the stdin, a null value is passed. but the pipe is not blocked.

Example

$ node ./myScript.mjs | ./myOtherScript.mjs
> hello world onstdin

Executing the script without the first step will pass null in to myOtherScript.mjs.

$ node ./myOtherScript.mjs
> BOOM !

Force blocking

When the -F or --force argument are passed the waiting for a chunk to be read to the end of a stream is enforced.

$ node ./myOtherScript.mjs -F
> 

API

onstdin(cb:() => void, enc:string = 'utf8'): void

| Parameters | description | | ---------- | ------------------------------------------------------ | | cb | the callback function | |enc| the encoding (utf8 by default)|

License

MIT