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

idle-queue-worker

v0.0.9

Published

Simple queue worker based on requestIdleCallback

Readme

#IdleQueueWorker

(WARNING! Still experimental library!)

Simple async queue implementation for low priority background tasks, such as analytics sending, data collecting.

Queue processing implemented over window.requestIdleCallback (shim included) that provides task processing on the main event loop, without impacting latency-critical events.

This module has no any external dependencies and some part of code base already used in production, enjoy.

Installation

  1. npm install --save idle-queue-worker
  2. Use with your favorite module bundler such (e.g. Webpack, Browserify, etc)

Documentation

Module provides a few interfaces: ForEachable, Mapable, Foldable. If you want to create your own interface, use QueueWorker and object composition concept.

For lot of cases you just need ForEachable interface and only two methods:

forEach → for dequeued data processing

enqueue → for passing some data to the queue.

##API

QueueWorker<T>(isReady?:() => boolean, timeout?:number, queue?:Array<T>)

Params ( aka queueWorkerArgs):

  • isReady — call before each attempt of queue item processing. If result is falsy, then next new work will be sheduled.
  • timeout (given in ms) — minimum time that must pass before calling the callback function.
  • queue — not recommended for use in real tasks. Only for testing usage.

Methods:

  • .register(callback: (item:T) => any):void — callback function for queue processing.
  • .enqueue(item:T):void — add item at the end of the queue.

Example:

import { QueueWorker } from 'idle-queue-worker/lib';

const worker = new QueueWorker();

worker.register(x => x * x);
worker.enqueue(2);

Abstract(...queueWorkerArgs)<T,R>

Methods:

  • .enqueue(item:T):void — proxy of queueWorker method
  • .pipe(queue:AnotherQueue):AnotherQueue — enqueue result of callback function to next queue

You can't construct Abstact instance directly, use classes below.

ForEachable(...queueWorkerArgs)<T>

Methods:

  • .forEach(callback: (item:T) => any):void — callback function applied for each dequeued element

Example:

import { ForEachable } from 'idle-queue-worker/lib';

const worker = new ForEachable();

worker.forEach(x => x * x);

Mapable(...queueWorkerArgs)<T,R>

Methods:

  • .map(callback: (item:T) => R):Self — a → b callback function
  • .take(count:number):Promise<Array<R>> — take first N processed items of queue
  • .takeUntil(predicate:(item:R) => boolean):Promise<Array<R>> — collect data until predicate result is falsy, then resolve result

Example:

import { Mapable } from 'idle-queue-worker/lib';

const worker = new Mapable();

worker
	.map(x => x * x)
	.take(10)
	.then(result => send(result));

Foldable(...queueWorkerArgs)<T,R>

Methods:

  • .fold(callback:(accumulator:R, item:T) => R, initialValue:R):Self — same as Array.prototype.reduce function
  • .foldUntil(count:number):Promise<R> — foldResult until predicate falsy

Example:

import { Foldable } from 'idle-queue-worker/lib';

const worker = new Foldable();

worker
	.fold((sum, value) => sum * value, 1)
	.foldUntil(sum => sum > 10)
	.then(result => send(result));

Piping:

You can pass the results of one queue to next queue just call .pipe method of ForEachable, Mapable, Foldable instances. There is many opportunities to determine your data flow with queues without pain.

Example:

import { ForEachable, Mapable, Foldable } from 'idle-queue-worker/lib';

const mapableWorker = new Mapable();
const forEachableWorker = new ForEachable();
const foldableWorker = new Foldable();

foldableWorker
    .fold((result, element) => result + element, 0)
    .foldUntil(result => result > 10)

mapableWorker
    .map(e => e * 2)
    .pipe(foldableWorker)
    .pipe(forEachableWorker)
    .forEach(e => console.log(e));

mapableWorker
    .take(5)
    .then(result => console.log('DONE!'));

##TODO

  • Live examples
  • A lot of improvements!