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

cachallel

v0.1.3

Published

For making idempotent calls in parallel and caching their responses

Downloads

13

Readme

Cachallel

Wrapper for managing high volume of duplicate idempotent asynchronous requests in JavaScript & TypeScript.

With basic caching

When you have a high volume of duplicate, overlapping, idempotent requests. If your application is making a number of requests with the same inputs, and the requests are idempotent, caching can be helpful to avoid unnecessary computation. If these requests are long-running and many duplicate requests are made before a response is cached for that request, there can be a lot of wasted computation.

Here is an example timeline only using caching. Requests 1, 2, 3, and 4 all have the same input and will receive the same output.

time
request 1
  -> cache miss
  -> make call to external service
    |
    | request 2
    |   -> cache miss
    |   -> make call to external service
    |     |
    |     | request 2
    |     |   -> cache miss
    |     |   -> make call to external service
    |     |     |
    |     |     |
    |     |     |
     -> request 1 resolved, update cache
          |     |
          |     | request 4
          |     |   -> use cached response from request 1
          |     |
           -> request 2 resolved, update cache
                |
                |
                 -> request 3 resolved, update cache

When requests 2 and 3 are made, request has not finished, so the cache will not be populated. There are two unfortuante outcomes of this approach:

  1. Requests 2 and 3 will waste resources by performing the same expensive and long-running request 1 is triggering.
  2. When request 1 is fulfilled, there is enough information to fulfill requests 2 and 3, but instead requests 2 and 3 will not resolve until they get a response from the external service.

With Cachallel

Cachallel optimizes for overlapping, duplicate requests by letting subsequent requests latch onto an existing Promise from a previous request.

request 1
  -> cache miss
  -> no pending Promise for this input
  -> make call to external service
    |
    | request 2
    |   -> cache miss
    | <--- attach to request 1's Promise
    |
    | request 3
    |   -> cache miss
    | <--- attach to request 1's Promise
    |
    |
    |
     -> request 1 resolved
       -> update cache
       -> request 2 resolved
       -> request 3 resolved

request 4
  -> use cached response from request 1

Example usage

import axios from "axios";
import { RedisClient } from "redis";
import { RequestManager, RedisCacheManager } from "cachallel";

async function getResourceFromSlowApi(
  id: number,
): Promise<{ id: number; name: string }> {
  return await axios.get(`external.service/resource/${id}`);
}

const redisClient = new RedisClient({ host: "127.0.0.1" });

const slowApiManager = new RequestManager(
  getResourceFromSlowApi,
  new RedisCacheManager(redisClient),
);

export default async function call(id: number) {
  return await slowApiManager.call(id);
}