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

yaspr

v1.0.2

Published

Yet another sequential promise resolver

Downloads

32

Readme

YASPR (Yet Another Sequential Promise Resolver)

Is Promise.all causing failures when you need to make 100s of asynchronous network calls? Do you get random file errors when writing multiple files at the same time? Do you need your async methods to be called in a specific order?

Node's Promise.all method will run all of your async methods in parallel which can cause network or file system errors. The method also prevents you from guaranteeing what order the functions are called. YASPR aims to solve these issues by

Install

npm install yaspr

Use

TypeScript

import { sequentialPromises } from "yaspr";

interface Params {
  name: string;
  timeout: number;
}

// Tracks the number of times the function was called
let count = 0;

// Async function that will will wait the designated timeout, print stuff, and return the number of times this function was called
async function someAsyncFunction(params: Params) {
  return await new Promise<number>(resolve => {
    setTimeout(() => {
      count += 1;
      console.log(`Name: ${params.name}, Timeout: ${params.timeout}`);
      resolve(count);
    }, params.timeout);
  });
}

async function run() {
  // Promise.all will resolve the shortest timeouts first.
  // YASPR will resolve in the order they are received.
  const params: Array<Params> = [
    { name: "Michael", timeout: 1000 },
    { name: "Jim", timeout: 500 },
    { name: "Pam", timeout: 750 },
    { name: "Dwight", timeout: 501 }
  ];
  console.log("Running using `Promise.all`. Output order based on timeout");
  console.log(await Promise.all(params.map(someAsyncFunction)));
  count = 0;
  console.log("Running promises sequentially");
  console.log(await sequentialPromises(params, someAsyncFunction));
}

(async () => await run())();

Develop

Get

git clone https://[email protected]/MikeWestbrook/MikesNodeModules/_git/yaspr

Build

npm run build

Watch

npm run watch

Run Sample

Runs a simple example. npm run sample