sindresorhus/p-queue

Promise queue with concurrency control

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 16th, 2026
Created on October 28th, 2016
Open Issues & Pull Requests: 7 (+0)
GitHub issues: Enabled
Number of forks: 221
Total Stargazers: 4,277 (+0)
Total Subscribers: 18 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.4 days
Mean response time: 276.4 days
90th percentile: 835.9 days
Tracked items: 71

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 760 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • help wanted (12)
  • enhancement (9)
  • bug (2)
  • documentation (1)
  • question (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

p-queue is a promise queue with concurrency control.

The tool solves the problem of managing asynchronous operations that need to be executed with a limit on how many can run simultaneously. It works by accepting promises or functions that return promises, queuing them internally, and executing them according to a specified concurrency limit. This prevents overwhelming system resources or hitting rate limits when dealing with many async tasks.

Developers should choose this tool when building applications that need to throttle concurrent operations, such as API clients making multiple requests, batch processing systems, or any scenario where uncontrolled parallelism would cause problems. It suits projects ranging from simple scripts to complex applications that require fine-grained control over async execution. The tool is particularly valuable for Node.js environments where managing promise concurrency is a common requirement.

The project maintains a steady stream of updates addressing edge cases and user-reported issues. Pull requests receive timely review and feedback from maintainers. The codebase demonstrates attention to code quality through consistent refinement of existing functionality rather than rapid feature expansion. Documentation is actively maintained to reflect the current state of the tool and address common usage patterns.