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 🙏

© 2025 – Pkg Stats / Ryan Hefner

typescript-async-timeouts

v1.0.2

Published

Typescript future timeout utils

Readme

Install

$ npm install typescript-async-timeouts --save

or

$ yarn add typescript-async-timeouts

Direct link to npmjs.com

The problem 1: managing timeouts

Too many times we have to manage the timeouts. Keeping the timeout result somewhere and managing to clean it up. Aswell providing asynchronous method and keeping the promises increases the boulerplate. To solve this there are two methods:

  1. runAsyncLater - consumes asynchronous method returning promise
  2. runLater - consumes blocking method
  • Both have two parameters: function and number to run timeout with
  • Timeout defaults to zero, which means it creates new promise and runs when browser resources are free
  • Both returns promise with the value the consumed method provies with method cancel() to cancel the timeout

So, instead of:

try {
  let timeout = null;
  const result = await new Promise((resolve, reject) => {
    timeout = setTimeout(() => async () => {
      try {
        const result = await myAsyncCall();
        resolve(result);
      } catch (error) {
        reject(error);
      }
    }, 1)
  });
// when we would like to cancel
  if (timeout != null) {
    clearTimeout(timeout)
  }
} catch (error) {
  concole.error(error);
}

We could run

try {
  const result = runAsyncLater(myAsyncCall, 1)
  result.cancel(); // to cancel the result
  await result; // to get the result
} catch (error) {
  console.error(error);
}

Short, right? Also, there is a ashortcut to synchronous call

try {
  const result = runLater(() => { return "OK"; }, 1);
  result.cancel(); // to cancel the result
  await result; // to get the result
} catch (error) {
  console.error(error);
}

The problem 2: managing timeouts and iterating asynchronously

I have really long array to iterate or heavy logic which needs to be run on ech row and I would not like to block the browser, So, there is a way to iterate asynchronous way. With two methods:

To solve the problem there are two methods:

  1. iterateAsyncLater - consumes asynchronous method returning promise
  2. iterateLater - consumes blocking method
  • Both have three parameters:
    1. array to parse
    2. consumer method
    • iterateAsyncLater - (value: ValueType, index: number, cancel: () => void) => Promise<any>
    • iterateLater - (value: ValueType, index: number, cancel: () => void) => any
    1. timeout in milliseconds (defaults to 0, which means the iteration is executed when browser resoures are free)
  • Both return promise with void but have method cancel in it.
  • Both consumer method cancel can be called any time to interrupt the iteration (in that case the promise returned by the call will also fail)

Basic syntax:

const runnable = iterateAsyncLater([...long_array], async (value, index, cancel) => {
  // do some magic stuff or call cancel();
});
runnable.cancel() // If I decied not to go this way
await runnable; // to wait until it runs

Or when the run is not async

const runnable = iterateLater([...long_array], (value, index, cancel) => {
  // do some magic stuff or call cancel();
});
runnable.cancel() // If I decied not to go this way
await runnable; // to wait until it runs