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

schedulerjs

v1.2.0

Published

A promise execution flow control library

Downloads

15

Readme

scheduler.js

A wrapper around Promise to control the execution flow

Build Status

License

Released under MIT License

Tests

Install mocha : npm install -g mocha Start tests with : npm test

Sequence

Sequence will execute Promises in serie

Example :

let seq = new Sequence();

seq
    .next(() => {
        return promise;
    })
    .delay(500)
    .next(() => {
        return new Promise((resolve, reject) => {
            resolve();
        });
    })
    .start();

seq.on('started', () => {
    console.log('Sequence started');
});

seq.on('next', (pos, total) => {
    console.log(`${pos} / ${total}`);
});

seq.on('error', err => {
    console.log(`A promise rejected with ${err}`);
});

seq.on('stopped', () => {
    console.log('Sequence stopped');
});

seq.on('finished', () => {
    console.log('Sequence finished');
});

API

  • constructor() initializes the sequence
  • next(Function callback) → Sequence adds a function to the queue
  • delay(Number number) → Sequence adds a timeout function to the queue
  • stop() stops the sequence
  • start() starts the sequence

Events

  • error(Object err) triggered when a Promise rejected
  • finished() triggered when all the Promise were finished
  • next(Number position, Number total) triggered when one promise finished.
  • started triggered when the sequence was started
  • stopped triggered when the sequence was stopped

Scheduler

Scheduler will execute Sequences in parallel

Example :

let scheduler = new Scheduler();

let seq1 = new Sequence();
let seq2 = new Sequence();

seq1
    .next(...)
    .delay(500)
    .next(...);

seq2
    .next(...)
    .next(...);

scheduler
    .add(seq1)
    .set('othername', seq2) // sets scheduler.othername to seq2
    .start();

API

  • constructor() initializes the scheduler
  • add(Sequence seq) → Scheduler adds a sequence to the parallel queue
  • set(String name, Sequence seq) → Scheduler same as add, but sets the reference inside the scheduler
  • start() starts all the sequences
  • stop() stops all the sequences

Events

  • error(Object err) triggered when one sequence triggered error
  • started triggered when the scheduler was started
  • finished triggered when all the sequences triggered finished
  • stopped triggered when the scheduler was stopped