p-map VS delay

p-map is a lightweight library that helps you handle asynchronous operations on arrays with controlled concurrency. It allows you to map over an array of promises and specify a limit on the number of concurrent operations. This is particularly useful when you need to perform tasks like fetching data from multiple URLs, processing files, or interacting with APIs, as it helps prevent overwhelming your server or exceeding API rate limits. By using p-map, you can strike a balance between speed and resource management, ensuring that your application remains stable and responsive under load.

p-map

Manually creating a Promise can look challenging, but you don't have to do that if you stick to async/await and Promise-based APIs. For example, you can use the npm package delay for a promisified version of setTimeout.

`git log --graph --decorate --oneline` is specific to a branch of a repository. Github Network shows the relationship between forks. It is similar but really the question answered by it is "what and where is the work being done" and "what is the relationship between work being done and this repository I'm looking at". It sucks that Network is buried, I think it should be much more accessible.

Eg https://github.com/sindresorhus/delay/network tells me that this work is being maintained actively, but most forks are not merging back. Another one might tell me work on the main fork is stalled, and many users are now doing PRs against a fork of the original.

To make sure last action is ended before doing another one, I add some delay between actions using delay.