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

abortcontroller-chain

v2.0.2

Published

Simple utility to chain an AbortController to one or more AbortSignals.

Downloads

200

Readme

Chain an AbortController to multiple AbortSignals

npm GitHub Workflow Status license Codecov

Chain multiple signals into one controller: if any of the signals aborts, the controller will be aborted. This is particularly useful since most APIs only accept a single AbortSignal input (fetch(), axios, the AWS SDK, etc).

Works with browsers, NodeJS (16+), and spec-compliant polyfills.

Usage

At a minimum, you must pass one or more AbortSignals. However, the controller is optional: if a controller is not passed in, one will be created and returned.

import { chainAbortController } from "abortcontroller-chain";

// use your own controller
chainAbortController(controller, signal1, signal2, signal3);

// auto-create the controller
const controller = chainAbortController(signal1, signal2, signal3);

Why

Say you're passing an AbortSignal into a long-running piece of code so you can end early if needed:

async function pollSomething(signal: AbortSignal) {
  while (!signal.aborted) {
    // keep polling until the signal says stop
  }
}

But wait! You want to make an HTTP request with a deadline of 10 seconds:

const TEN_SECONDS = 10 * 1000; // ms
async function pollSomething(signal: AbortSignal) {
  while (!signal.aborted) {
    // abort after 500ms
    const abortController = new AbortController();
    setTimeout(() => abortController.abort(), TEN_SECONDS);

    // do the fetch...
    const result = await fetch("/something-something", {
      // wait, this doesn't take into account the signal
      // passed to pollSomething()
      signal: abortController.signal,
    });

    /* ... */
  }
}

Wouldn't it be great if the fetch-specific abortController could be aborted by the outer signal? That's easy with the abortcontroller-chain package:

import { chainAbortController } from "abortcontroller-chain";

const TEN_SECONDS = 10 * 1000; // ms
async function pollSomething(signal: AbortSignal) {
  while (!signal.aborted) {
    const abortController = new AbortController();
    chainAbortController(abortController, signal);
    setTimeout(() => abortController.abort(), TEN_SECONDS);

    // do the fetch...
    const result = await fetch("/something-something", {
      // hooray! both signals are now respected
      signal: abortController.signal,
    });

    /* ... */
  }
}

You can further simplify the creation:

const abortController = chainAbortController(signal);
setTimeout(() => abortController.abort(), TEN_SECONDS);