sequent-promises
Advanced tools
Call promises one by one, ignoring the state (fulfilled or rejected). and returning the collected data in the tuple { results, errors }.
npm
npm install sequent-promises
yarn
yarn add sequent-promises
import sequentPromises, { isNotRunningError } from 'sequent-promises';
const result = 'result';
const error = new Error('error');
const promiseResolve = () => Promise.resolve(result);
const promiseReject = () => Promise.reject(error);
sequentPromises([promiseResolve, promiseReject, promiseResolve]).then(({ results, errors }) => {
console.log(results); //[result, result]
console.log(errors); //[Not running: Promise was not running]
console.log(isNotRunningError(errors[0])); //true;
});
npm test
Krivega Dmitriy
Contributions, issues and feature requests are welcome!
Feel free to check issues page. You can also take a look at the contributing guide.
Copyright © 2020 Krivega Dmitriy.
This project is MIT licensed.
FAQs
sequentPromises resolves Promises sequentially
The npm package sequent-promises receives a total of 1,079 weekly downloads. As such, sequent-promises popularity was classified as popular.
We found that sequent-promises demonstrated a healthy version release cadence and project activity because the last version was released less than 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
Research
Socket researchers have discovered malicious npm packages targeting crypto developers, stealing credentials and wallet data using spyware delivered through typosquats of popular cryptographic libraries.
Security News
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.
Security News
A Stanford study reveals 9.5% of engineers contribute almost nothing, costing tech $90B annually, with remote work fueling the rise of "ghost engineers."