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

handle-race-condition

v3.0.2

Published

Module that solves race condition problem with async calls

Downloads

6,601

Readme

handle-race-condition

Module that accepts an async function, and returns an async function that can be called any number of times in parallel, but will always resolve/reject with result of the latest call.

  • Super simple to use
  • No dependencies on any other library.
  • Works with any async function that returns a Promise
  • Supports AMD

Race condition

There are times when you call an async function multiple times but the ouput may not come in the same order as it was called, i.e, the first call can be resolved after the second call. This is called race condition and you can solve it using this simple module.

How to install

npm i handle-race-condition

Example usage

Consider the example below:

const someAsyncFunction = (time, order) => {
    return new Promise((resolve) => {
        setTimeout(() => {
            resolve(order);
        }, time);
    });
};

Here someAsyncFunction is an async function whose output can resolve at different times depending on time. You can think of this time as the time required for an ajax response.

Now lets call this function multiple times:

someAsyncFunction(500, 1).then((order) => { console.log(order) });
someAsyncFunction(200, 2).then((order) => { console.log(order) });
someAsyncFunction(50, 3).then((order) => { console.log(order) });
someAsyncFunction(400, 4).then((order) => { console.log(order) });
someAsyncFunction(100, 5).then((order) => { console.log(order) });

As you can see the output below is not in the same order as it was called:

3
2
4
1
5

Now lets use our module:

import handleRaceCondition from 'handleRaceCondition';

const someAsyncFunction = (time, result) => {
    return new Promise((resolve) => {
        setTimeout(() => {
            resolve(result);
        }, time);
    });
};

const getResult = handleRaceCondition(someAsyncFunction);

getResult(500, 1).then((result) => { console.log(result) });
getResult(200, 2).then((result) => { console.log(result) });
getResult(50, 3).then((result) => { console.log(result) });
getResult(400, 4).then((result) => { console.log(result) });
getResult(100, 5).then((result) => { console.log(result) });

You pass the desired async function to handleRaceCondition() and it will return another async function which when called multiple times will always resolve for the last call. The output, as you can see now, is resolved when the last call is resolved.

5
5
5
5
5