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

controlstream

v0.0.6

Published

read Streams that have a read function, and pipe to multiple destinations

Downloads

11

Readme

ReadStream

Install

npm install controlstream

create a ReadStream

var controlStream = require('readstream').controlStream
var cs = new controlStream()

fs.createReadStream('file').pipe(cs)

cs.read(50, function(err, data){
	//first 50 bytes are available in data
	
})

move to a certain location

cs.curser = 100
cs.read(50, function(err, data){
	//read bytes 100 to 150	

})	

pipe to a destination

var controlStream = require('controlstream').controlStream
var cs = new controlStream()

fs.createReadStream('file').pipe(cs).pipe(dest)

pipe to multiple destinations

var controlStream = require('controlstream').controlStream
var cs = new controlStream()

fs.createReadStream('file').pipe(cs)

cs.pipe(dest1)
cs.pipe(dest2)

Advanced

var controlStream = require('controlstream').controlStream
var cs = new controlStream({slice:true})

if you pass options {slice:true}, every time you read, that data is no longer in the buffer

cs.read(10, function(err, data){
	//read a header and decide what to do with it
	cs.pipe(dest)
	//pipe the remaining bytes to a destination
	cs.pipe(dest2)
	//pipe remaining bytes to another destination
})

only piping to one destination? or is this the last destination you are piping to?

cs.pipe(dest, {slice:true})
//when cs is done piping, there will be nothing left in the buffer

describe pace and cadence of the pipe (bytes per second)

var controlStream = require('controlstream').controlStream
var cs = new controlStream()

fs.createReadStream('file').pipe(cs)

cs.pipe(dest1, {pace:50,cadence:1000})
//pipe at 50 bytes per second