Run promise-returning & async functions a specific number of times concurrently
Run promise-returning & async functions a specific number of times concurrently
$ npm install p-times
const pTimes = require('p-times');
(async () => {
const result = await pTimes(5, i => createFixture(`🦄-${i + 1}`));
console.log(`Created fixtures: ${result.join(' ')}`);
//=> 'Created fixtures: 🦄-1 🦄-2 🦄-3 🦄-4 🦄-5'
})();
Returns a Promise that is fulfilled when all promises returned from mapper are fulfilled, or rejects if any of the promises reject. The fulfilled value is an Array of the fulfilled values returned from mapper in order.
Type: number
Number of times to call mapper.
Type: Function
Expected to return a Promise or value.
Type: object
Type: number
Default: Infinity
Minimum: 1
Number of concurrently pending promises returned by mapper.
Type: boolean
Default: true
When set to false, instead of stopping when a promise rejects, it will wait for all the promises to settle and then reject with an aggregated error containing all the errors from the rejected promises.
FAQs
Run promise-returning & async functions a specific number of times concurrently
The npm package p-times receives a total of 16,969 weekly downloads. As such, p-times popularity was classified as popular.
We found that p-times demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.