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 🙏

© 2025 – Pkg Stats / Ryan Hefner

stream-scheduler

v1.1.3

Published

Schedule a job that reads and process a http(s) stream

Readme

stream-scheduler

This tiny module will allow you to stream a URL on an interval basis. It will report when is the last time it executed correctly, when it is the last time it encountered an error on the execution and whether is executing in that moment or not. On top of that, it will allow you to trigger the streaming job "out of schedule".

This component is very simple and specially useful when you need to run scheduled jobs to extract information from a URL. It is robust because it offers healthcheck information (so you could potentially return it in your server endpoint) and it is flexible, since it allows you to "manually" trigger the job, in case you need to.

The usage is quite simple. First, create an object with the following configuration. (All fields are optional, except for the url and the interval/schedule, since you need to specify at least one of these):

var options = {
  url: <the url to stream from>,
  interval: <your interval in seconds>,
  schedule: <your cron-like configuration>,
  onStartExec: <callback to execute when the job gets triggered>,
  pipeline: <list of streams to pass the url request execution through>,
  startNow: <forces the component to trigger the process inmediately>
}

The schedule field allows you to configure your job to run on a particular moment in time. It is using the node-schedule module, so you can visit their page to check your available options. A couple of useful examples of use are these:

var options = {
  ...
  schedule: {hour: 14, minute: 30, dayOfWeek: 0},
  ...
}

or a more cron-like format [MINUTE] [HOUR] [DAY OF MONTH] [MONTH OF YEAR] [DAY OF WEEK] [YEAR (optional)]:

var options = {
  ...
  schedule: '0 17 ? * 0,4-6',
  ...
}

Once you've configured the stream scheduler, you just need to require and initialise the stream-scheduler:

var ss = require('stream-scheduler');
ss.init(options);

After that you will be able to interact with the stream scheduler with the following functions:

ss.isExecuting(); //It will tell you if your streaming job is executing at the moment
ss.getLastExecutionTime(); //It will return the last time when it finished executing successfully
ss.startExecution(); //It will force the component to execute the job (unless it's already running)

You can find a good usage example here.

Please feel free to report bugs/create pull requests/give feedback.

Enjoy!