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

polling-stream

v3.0.0

Published

Emit a perpetual readable stream by providing a function that returns the next segment of the readable stream.

Downloads

11

Readme

polling-stream

Emit a perpetual readable stream by providing a function that returns the next segment of the readable stream.

build status

This module is a good if you want an perpetual read stream where you need to poll for changes to each new 'segment' of the stream. An example would be polling a database for changes at the end of a table.

Installation

This module is installed via npm:

$ npm install polling-stream

Example Usage

let pollingStream = require('polling-stream');
const initState = 0;
// poll every 2 seconds after each segment stream has finished
let s = pollingStream(getNextStreamSegment, initState, updateState, { interval: 2000 }});

// generate a stream of numbers from 0 to 13, in batches of 10 numbers
const batch = 10;
function getNextStreamSegment(start) {
    let i = start;
    let rs = Readable({
      objectMode: true,
      read: () => {
        // do a maximum of 14 elements
        if (i === 14) {
          rs.push(null);
          rs.emit('terminate');
          return;
        }
        rs.push(i);

        // just do 10 elements at a time
        if (++i >= batch) rs.push(null)
      }
    });
    return rs;
}

function updateState(curr) {
  return curr + 1;
}

s.on('data', console.log);
// Will print the numbers from 0 to 9, wait two seconds then print out
// the nunbers 10 to 13

API

pollingStream(getNextStreamSegmentFn, initState, updateStateFn, [opts])

Returns a new polling stream.

  • getNextStreamSegmentFn() - a function that returns the next segment of data in the perpetual stream. It returns a ReadableStream for the next segment of the stream. The function is passed the current state which is updated with every call to write() using the updateState() funciton.
  • initState - the initial state that will be passed to getNextStreamSegmentFn().
  • updateStateFn - Each time write() is called on (i.e. each time we get a chunk from the underlying stream) we call this to update our internal state. It will be given the chunk and the current state as arguments. are required to maintain this (e.g. database writes/reads).
  • opts - this will be passed to the constructor of the perpetual ReadableStream. It defaults to having { objectMode: true }, so set this to false if you're dealing with binary streams. There is also a field called interval which is the poll frequency. When the stream that gets returned from getNextStreamSegmentFn finishes, this delay (in milliseconds) will elapse, before the function gets called again. It defaults to 1000 milliseconds (1 second).

event('terminate')

If you want to actually terminate the perpetual stream you first have to end the stream (eg. stream.push(null), and then stream.emit('terminate').

event('sync')

The perpetual stream emits a sync event when the stream segment has closed. You can hook into this to do things like regular logging, stats reporting, etc.