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

sync-async-loops

v1.1.0

Published

a tool to help you controll asynchronous loops, speed things up, and make sure certain parts are executed in an orderly fashion while keeping the asynchronous nature of the loop

Downloads

6

Readme

sync-async-loops

The library purpose is to help you synchronise asynchronous loops in order to obtain a better performance

Synchronizer

const Synchronizer = require ('sync-async-loops')

const synchronizer = new Synchronizer() if you want to use your own Promise.all(data.map())

await new Synchronizer(data, (synchronizer, item, index, .....) => {})

  • the first argument in the callback is the synchronizer,
  • the rest of the arguments are the arguments for the callback from data.map()

synchronizer.sync(index)

Create a point from which the loops will be executed one by one,starting with the first index

It behaves as if the loop just started.

synchronizer.syncOnce(fn, param1, param2, param3........)

Calls an async function using the provided params, and for each call, it returns the same promise, making sure to make only one call for all the items that are being processed

synchronizer.waitAll(index, length?)

  • unlike sync, this one waits for all the loops to reach this point before letting them go

  • if we use Synchronizer(data, () => {}) instead of Promise.all(data.map()) then we can ommit the length paramter

Example 1

await Promise.all(
    data.map(async (item, index) => {
        resultsArrOne.push(item)
        await synchronizer.runOnce(sleepRandom, 'sleep', 'param1', 'param2')
        await synchronizer.sync(index)
        resultsArrTwo.push(item)
    })
)

Example 2

const findProjectsByUserNames = async (userNames) => {  
    const users = await usersRepositoy.findUsersByName(userNames)
    const userIds= [] 
    const projects = []
    await new Synchronizer( users, async (user, index) => {
        userIds.push(user.id)
        await synchronizer.waitAll(index)
        const userProjects = await synchronizer.runOnce(findProjectsByUserIds, 'getProjectUsers', userIds)
        const projectsMap = synchronizer.runOnce(mapProjects, 'mapProjectUsers', userProjects)
        const project = projectsMap.get(userId)
        projects.push({
            ...project, 
            userFullName: `${user.firstName} ${user.lastName}`
        })
    })
    return projects
}

const mapProjects (userProjects) => {
    const projectsMap = new Map()
    for (project of Projects){
        projectsMap.set(project.user.id, project)
    }
    return projectsMap
}