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 🙏

© 2026 – Pkg Stats / Ryan Hefner

bid.js

v1.0.1

Published

In-memory work queue

Readme

Bid.js

In-memory work queue

How to

Install

npm i bid.js

Import

import Bid from 'bid.js'

Use

// Creating new instances of our queue
const bid = new Bid();

// Set up a process callback
bid.setProcess((job, progress, done) => {
  // ..Logic
  const result = 'The job is done!';
  done(null, result);
});

// Add your first payload for queue
bid.add({some: "payload"});
/*
By the way this payload appears in job.payload
*/

API

new Bid( config )

| option| default | what for | | --- | --- | --- | | config.enumerate | false | Enumerate job.id instead of random id | | config.process | undefined | Callback function to handle the payload |

Bid instance

| option| usage | what for | | --- | --- | --- | | bid.setProcess | callback(job, progress, done) | Set the process callback| | bid.add | payload | Add new payload to queue | | bid.on | ('start', cb(job)) | Callback event on every job was started | | bid.on | ('finish', cb(job)) | Callback event on every job was finished | | bid.on | ('error', cb(job)) | Callback event on job was done with error | | bid.on | ('end', cb()) | Callback event on queue is ended |

Job

| option| value | what for | | --- | --- | --- | | job.id | string/id number | Job unique/serial id | | job.name? | undefined | Job string name | | job.done | boolean | Is the job already done without error | | job.finished | number | Unixtime job was finished | | job.created | number | Unixtime job was created | | job.progress | number | Job workflow progress percent | | job.payload | any | Job payload | | job.dead | boolean | Is job dead (timeout) | | job.result | any | Job result with which it was finished ( done(error?, result?) ) | | job.error | Error/string | Job error with which it was finished ( done(error?, result?) ) |

More helpfull

Also try to use it with typescript, just import Bid with all the types it uses

import Bid from 'bid.js'
import {
  BidProcess,
  BidCallback,
  BidEvent,
  BidStatus,
  BidJob,
  BidProcessJob,
  Done,
  Progress,
  BidConfig,
  BidError,
} from  'bid.js';

Tests

npm run test