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

shift.taskqueue

v1.0.6

Published

A simple javascript library that executes given tasks in a queue.

Downloads

41

Readme

A simple javascript library that executes given tasks in a queue.

Install

npm install --save shift.taskqueue

How it works

First you should instantiate a TaskQueue object. Then all it's left to do is push tasks to it. Note that tasks MUST ALWAYS be functions.

Pushed functions will be executed "first in first out" and they are never processed at the same time. Next function in line will be called only when the current one resolves (asynchronous) or returns (synchronous).

Pushed functions may or may not return a promise. If it does, task will be completed only when the promise resolves, calling then the next one in line.

Example

import TaskQueue from 'TaskQueue'; // const TaskQueue = require('TaskQueue');

let taskQueue = new TaskQueue();

taskQueue.push(func1).then(result => console.log(result));
taskQueue.push(func2).then(result => console.log(result));
taskQueue.push(func3).then(result => console.log(result));
taskQueue.push(func4).then(result => console.log(result));

setTimeout(() => {
    taskQueue.push(func2).then(result => console.log(result));
}, 1600);

setTimeout(() => {
    taskQueue.push(func3).then(result => console.log(result));
}, 5000);

function func1() {
    return new Promise(resolve => {
        setTimeout(() => {
            resolve('func1 done processing');
        }, 1000);
    });
}

function func2() {
    return new Promise(resolve => {
        setTimeout(() => {
            resolve('func2 done processing');
        }, 500);
    });
}

function func3() {
    return 'func3 done processing';
}

function func4() {
    return new Promise(resolve => {
        setTimeout(() => {
            resolve('func4 done processing');
        }, 200);
    });
}

Output

*Approximate accumulated processing time from the beggining.

after 1000 milliseconds ---> 'func1 done processing'
after 1500 milliseconds ---> 'func2 done processing'
after 1500 milliseconds ---> 'func3 done processing'
after 1700 milliseconds ---> 'func4 done processing'
after 2100 milliseconds ---> 'func2 done processing'
after 5000 milliseconds ---> 'func3 done processing'