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

deferq

v1.2.1

Published

A tiny, zero-dependency JavaScript library for queuing async actions when offline and automatically retrying them when connectivity returns.

Readme

deferq

A tiny, zero-dependency JavaScript library for queuing async actions when offline and automatically retrying them when connectivity returns.

  • Lightweight: ~30 lines of code
  • Zero dependencies
  • Concurrent retries: All queued actions run in parallel when back online
  • Flexible: Queue any async function by name

Ideal for simple offline support without the complexity of service workers.

Installation

Via npm

Install with: npm install deferq

Via CDN

<script src="https://app.unpkg.com/[email protected]/files/index.js"></script>

Usage

1. Initialize the library (once)

<script type="module">
  import { addToQueue, register } from 'https://cdn.jsdelivr.net/npm/[email protected]/index.js'; // Automatically registers the "online" listener
</script>

2. Queue actions when offline

async function createPost({ post }) {
  if (!navigator.onLine) {
    addToQueue('networkQueue', 'createPost' { post });
    showToast("Offline — we'll retry when you're back online.", 5);
    return;
  }

  const res = await fetch('/api/post', {
    method: 'POST',
    body: JSON.stringify({ post }),
    headers: { 'Content-Type': 'application/json' }
  });
  // handle response...
}

// Call your function as usual
createPost({ post: "Hello world!" });

3. Automatic retry

When the browser fires the "online" event, deferq:

  • Loads the queue from internal storage.
  • Executes all queued functions serially to avoid a thundering herd.
  • Removes successful actions.
  • Keeps persistent failures for the next online event.

No additional setup required.

API

addToQueue(key: string, fnName: string, payload: any)

Queues an action.

  • key: key for the queue (e.g., 'networkQueue', 'fetchQueue', 'transferQueue')
  • fnName: Name of the function as it was registered to deferq.
  • payload: Data to pass to the function when replayed

Example: addToQueue('networkQueue', 'createPost', { post: 'data' })

How It Works

  • When offline, use addToQueue instead of calling the function directly.
  • Actions are cached in internal storage under the given key.
  • On "online", deferq replays all actions serially.
  • Successful actions are removed; failed ones remain for future retries.

Notes

  • In v1.1.3, actions are no longer stored in localStorage to avoid pollution and XSS attacks.
  • Functions to queue must be pure functions and not use global state, for safety and proper application.
  • No built-in queue size limit (add your own in production if needed).
  • Works in all modern browsers.

Function Naming Requirement

For automatic retry to work, the calling function must have a name that appears in the stack trace.

Works:

  • Named function declarations: function createPost() {}
  • Named function expressions: const post = function createPost() {}

Does not work:

  • Arrow functions: const createPost = async () => {}
  • Anonymous functions

Recommendation: Use named functions for actions that may be queued offline.

License

MIT