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

@jrc03c/queue

v0.0.5

Published

`queue` is a simple queueing tool for JS.

Downloads

5

Readme

Intro

queue is a simple queueing tool for JS.

Installation

npm install --save https://github.com/jrc03c/queue

Usage

Node / bundlers:

const Queue = require("@jrc03c/queue")

Browser:

<script src="path/to/dist/queue.js"></script>

Then:

async function run(){
  const timeBetweenJobs = 1000
  const queue = new Queue(timeBetweenJobs)

  // Option 1: `append` an async function to the queue, which returns an ID; then
  // `retrieve` the result using the ID later.
  const id1 = queue.append(async () => {
    const response = await fetch(...)
    return await response.json()
  })

  const result1 = await queue.retrieve(id)

  // Option 2: Do both steps using the single `process` function.
  const result2 = await queue.process(async () => {
    const response = await fetch(...)
    return await response.json()
  })
}

run()

API

Queue

The Queue class is the primary tool in this library. As you append jobs (i.e., asynchronous functions) to the queue, the queue processes them one-at-a-time, in order, with a short pause after each job is finished.

Properties

jobs

An array of "jobs" where each job is a dictionary containing id and fn properties.

results

A dictionary of ID-value pairs.

interval

The thing returned from setInterval when .start() is called.

isRunning

A boolean indicating whether or not the queue is actively processing jobs.

timeBetweenJobs

A number indicating a time in milliseconds to wait after each job finishes before starting the next job.

Methods

new Queue(timeBetweenJobs=100)

The only argument to the Queue constructor is the amount of time (in milliseconds) to wait between jobs. The default value is 100 milliseconds.

.append(asyncFunction)

Appends an asynchronous function to the list of jobs to process and returns an ID that points to that job.

.retrieve(ID)

Returns a Promise that resolves to the output of the job.

.process(asyncFunction)

Returns a Promise that resolves to the output of the job. This function is exactly like calling .append(asyncFunction) and then .retrieve(ID).

.start()

Starts the processing of the list of jobs. Normally, this doesn't need to be called manually; it's called automatically as soon as a job is appended to the list of jobs.

.stop()

Stops the processing of the list of jobs. Any jobs that are being processed when this method is called will not be stopped; they will finish as usual and store their results. Normally, this doesn't need to be called manually; it's called automatically as soon as the job list becomes empty.

.destroy()

Stops the processing of the list of jobs and then sets all properties to null.