π¦ Aigle is an ideal promise library which is faster and more efficient than other libraries. It is a production-ready library that implements the Promise A+ standard.
License: MIT License
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
![greenkeeper[bot] avatar](https://avatars.githubusercontent.com/in/505?v=4 "greenkeeper[bot]")
First of all, thanks for this library, it looks amazing!
I discovered it because I'm async contributor and I needed a Promise based alternative.
The issue is related with p-progress, that reports you information about tasks progress.
For example: https://github.com/sindresorhus/p-progress/blob/master/example.js
Because you need to manually increment the progress counter, could be easy do this internally into aigle methods for increment the counter based in each step of the .parallel, .series, .each, .etc methods.
It could be expose as .onProgress method for get information about the job state.
The thing is, do you think make sense and could be useful expose this information?
When I use Aigle to promisifyAll(require('fs')) I end up with multiple leveled Async functions. For example, for readFile() I end up with:
readFile: [Function],
readFileAsync: [Function],
readFileAsyncAsync: [Function],
readFileAsyncAsyncAsync: [Function],
Path seems to fair worse on almsot all functions:
resolve: [Function: resolve],
resolveAsync: [Function],
resolveAsyncAsync: [Function],
resolveAsyncAsyncAsync: [Function],
resolveAsyncAsyncAsyncAsync: [Function],
resolveAsyncAsyncAsyncAsyncAsync: [Function],
resolveAsyncAsyncAsyncAsyncAsyncAsync: [Function],
resolveAsyncAsyncAsyncAsyncAsyncAsyncAsync: [Function]
Why?
PS: bluebird does not seem to suffer from this. I get one Async promise-returning function for each function in a library.
return Aigle.map([1.1, 1.4, 2.2], n => Aigle.delay(10, n * 2)) // [2.2, 2.8, 4.4]
.uniqBy(n => Aigle.delay(10, Math.floor(n))) // [2.2, 4.4] ==> [2,4]
.sum() // 6.6 ==> [6]
.times() // [0, 1, 2, 3, 4, 5];
.then(value => console.log(value)); // [0, 1, 2, 3, 4, 5];
If unhandled rejection is not caught, it should be shown on console.
const Aigle = require('aigle');
global.Promise = Aigle
Promise.resolve(Promise.resolve(1)).then(value => console.log('the resolved value is ',value));The code above will console
the resolved value is Aigle { _resolved: 1, _value: 1, _key: undefined, _receiver: undefined, _onFulfilled: undefined, _onRejected: undefined, _receivers: undefined }
I think the correct console should be the resolved value is 1γ
https://github.com/suguru03/aigle/blob/master/lib/aigle.js#L3633
should add a judge here
function _resolve(value) {
if (value instanceof Aigle) {
return value;
}
const promise = new Aigle(INTERNAL);
promise._resolved = 1;
promise._value = value;
return promise;
}
Hello !
I encountered an issue with aigle when trying to use it in production.
I am developing a React app based on Create React App. When I try to build it in production, it fails at minification step because of aigle as its code is not compiled for ES5. You can have more details here: npm run build fails to minify
Could you publish a pre-compiled version of aigle compatible with ES5 ?
Thanks a lot !
This looks very impressive π I suggest splitting out Promise spec implementation and additions into separate modules so that the Promise could just be used as a polyfill.
I just realized it. It causes from v1.11.0.
This is in an angular application:
let uri = await Aigle.promisify(this.carImage.getBase64)(Jimp.MIME_PNG)
where this.carImage is an image from jimp
Results in:
Error: Uncaught (in promise): TypeError: this.getBuffer is not a function
0.19.4 to 0.19.5.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
buble is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 34 commits.
a4d66ef -> v0.19.508be12b Transpile U+2028 and U+2029 (json-superset)59d1127 Hopefully fix travis file syntax1593577 Try to make register test run in node485d74e0 Stricter and faster travis setupeb0f3c5 Add simple test for register.js functionality7ddf225 Correctly transpile computed xor spread properties7e7e9e7 Add class /@PURE/ annotations to tests8e87c35 Add /@PURE/ comment annotation to class IIFE24b1fab Allow disabling spread properties transpiling9a79122 Add objectRestSpread support dataab84650 Add support info for async/awaitbc02c36 Add support data for newer engine versionsf311900 Mark Safari 9 as not supporting argument destructuringfd0cbb5 Mark more engines as not supporting const/letThere are 34 commits in total.
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Hello
I am not sure if typescript is fully completed but when I try to import Aigle as mentioned in the doc, I am getting Aigle as undefined which fails all my calls. E.g. Agile.eachLimit throws an error 'Cannot read propery eachLimit of undefined'. However the below code works fine.
import * as Aigle from 'aigle'
then Aigle.default.eachLimit
3.4.10 to 3.5.0.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
uglify-js is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Β
The new version differs by 8 commits.
fd78859 v3.5.0143f905 fix corner case in sequences (#3350)f2286c3 enhance unsafe for Array (#3349)b9615f7 improve compress performance (#3348)c520e99 enhance comparisons (#3347)615ae37 introduce assignments (#3345)7aa7f21 fix corner case in evaluate (#3344)4430a43 fix corner case in inline (#3343)See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Hi @suguru03 have u thought about adding typescript types for the project?
const _ = require('lodash');
const Aigle = require('aigle');
Aigle.mixin(_);
function asyncFunc(n) {
return new Promise(resolve => setTimeout(resolve, 10, n * 2));
}
main=async function() {
// example 1
const array = [1, 2, 3];
const result_1 = await Aigle.map(array, asyncFunc);
// example 2
const result_2 = await Aigle.chain(array)
.map(asyncFunc)
.sum()
.value();
// or
const result_3 = await Aigle.resolve(array)
.map(asyncFunc)
.sum();
const result_4 = await Aigle.map(array, asyncFunc)
.sum();
console.log(result_1,result_2,result_3,result_4)
}()
// ==> [ 2, 4, 6 ] undefined 12 12
// should result_2 == result_4
βββ¬ [email protected]
β βββ [email protected]
βββ [email protected]
I was checking about Aigle.parallel and I found at least exist 3 methods for do technically the same, but using different input. Specifically I'm referrencing this methods:
- Aigle.all
- Aigle.props
That basically could be expose just in one
- Aigle.parallel
The think I'm suggesting is avoid expose overhead methods for make easy use the same method all the time, because:
For example, taking lodash as example, see lodash.forEach method. You can use it for objects or arrays, and it's so powerful; the point is it is not distinguishing between two methods; just one for Collection an abstraction of data type that include array and object (like Iterable).
What do you think?
Now, Aigle.retry only has integer times option. It should have the same functionality as async.retry.
http://caolan.github.io/async/docs.html#retry
| Branch | Build failing π¨ |
|---|---|
| Dependency | uglify-js |
| Current Version | 3.0.15 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As uglify-js is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Β
The new version differs by 23 commits.
4231f73 v3.0.16da2de35 add comment about quote_style and gzip (#2092)41beae4 cache web assets between CI runs (#2089)82db918 fix CLI parsing of --source-map content (#2088)3dc9e14 add Node.js 8 to Travis CI (#2086)fed0096 allow expect_stdout to specify Error (#2087)2bdc880 fix variable accounting in inline (#2085)5ef7cb3 suppress false positives for-in loops (#2080)4ad7b1d fix portability of sandbox.run_code() on Node.js 0.1x (#2078)9186859 fix non-string parameters (#2076)47c0713 report test/ufuzz.js failures in process.stderr (#2074)293c566 marshal mangle[.properties].reserved from non-Array values (#2072)9c30640 fix iteration over object with inherited properties (#2068)9db0695 fix cascade on multi-branch evaluations (#2067)f2af093 fix CLI output corruption (#2061)There are 23 commits in total.
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
I am a newbie for Callback, Promise, Async/Await.
But I understand that we use Async/Await to wait running before to continue.
I tried
async function aigleFn(array) {
const users = await Aigle.map(array, val=>{
.....
});
console.log('Done!')
}
aigleFn([1,2,3,4,5])
----
async function nativeFn(array) {
const users = await array.map( val=>{
.....
});
console.log('Done!')
}
nativeFn([1,2,3,4,5])What difference?
These functions will be renamed.
These functions are the almost same as pickBy/omitBy, but shorthand will be different.
// current
const collection = {
a: { bool: 0 },
b: { bool: 1 },
c: { bool: 1 }
};
Aigle.pick(collection, 'bool'); // { b: {}, c: {} }
_.pick(collection, 'bool'); // {}
_.pickBy(collection, 'bool'); // { b: {}, c: {} }
// after
Aigle.pick(object, 'a'); // { a: {} }
Aigle.pick(object, 'bool'); // {}
Aigle.pickBy(object, 'bool'); // { b: {}, c: {} }const redis = require('redis');
Aigle.promisifyAll(redis);
const key = 'test';
redis.hsetAsync(key, 1)
.then(() => redis.hgetAsync(key))
.then(value => console.log(value)); // 1
must createClient
const redis = require('redis').createClient()
Aigle.promisifyAll(redis)
Could I test Aigle on JsFiddle?
Please help me
Add a default iterator which has the same functionality as lodash filter's iterator.
Aigle.map([1, 2, 3, 4], n => Aigle.resolve(n % 2))
.filter()
.then(console.log); // [1, 1]1.14.2 to 1.14.3.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
π Changelog
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
6.0.2 to 6.1.0.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
options parameter (@plroebuck).jsonc extension (@sstephant)These are soft-deprecated, and will emit a warning upon use. Support will be removed in (likely) the next major version of Mocha:
this.skip() in "before each" hooks (@juergba)--allow-uncaught for uncaught exceptions thrown inside hooks (@givanse)and some regressions:
Suite cloning by copying root property (@fatso83)The new version differs by 28 commits.
f4fc95a Release v6.1.0bd29dbd update CHANGELOG for v6.1.0 [ci skip]aaf2b72 Use cwd-relative pathname to load config file (#3829)b079d24 upgrade deps as per npm audit fix; closes #3854e87c689 Deprecate this.skip() for "after all" hooks (#3719)81cfa90 Copy Suite property "root" when cloning; closes #3847 (#3848)8aa2fc4 Fix issue 3714, hide pound icon showing on hover header on docs page (#3850)586bf78 Update JS-YAML to address security issue (#3845)d1024a3 Update doc examples "tests.html" (#3811)1d570e0 Delete "/docs/example/chai.js"ade8b90 runner.js: "self.test" undefined in Browser (#3835)0098147 Replace findup-sync with find-up for faster startup (#3830)d5ba121 Remove "package" flag from sample config file because it can only be passes as CLI arg (#3793)a3089ad update package-lock75430ec Upgrade yargs-parser dependency to avoid loading 2 copies of yargsThere are 28 commits in total.
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Aigle functions should return the same order (it is not ensured by engines).
(async () => {
const obj1 = {
task1: Aigle.delay(30, 1),
task2: Aigle.delay(20, 2),
task3: Aigle.delay(10, 3)
};
const res1 = await Aigle.props(obj1);
console.log(res1);
// { task3: 3, task2: 2, task1: 1 }
// β
// { task1: 1, task2: 2, task3: 3 }
const obj2 = {
task1: 1,
task2: 2,
task3: 3
};
const res2 = await Aigle.mapValues(obj2, val => Aigle.delay(val * 10, val));
console.log(res2);
// { task3: 3, task2: 2, task1: 1 }
// β
// { task1: 1, task2: 2, task3: 3 }
})();v1.11
promisify a function that callback function has More than two params
e.q.
const { exec } = require('child_process');
const exec_1 = require('util').promisify(exec);
const exec_2 = require('aigle').promisify(exec);
const cmd = 'ls 1>&2';
exec_1(cmd).then(raw=> console.log('exec 1=>',raw)).catch(e=>console.log('exec 1 error=>',e));
exec_2(cmd).then(raw=> console.log('exec 2=>',raw)).catch(e=>console.log('exec 2 error=>',e));
.result
exec 1 => { stdout: '', stderr: 'a.file'}
exec 2 =>
Would you be able to re-run the benchmarks and update them to reflect how fast Aigle is and how it compares to native-async-await in both Node 10.x and Node 11.x
I believe there have been significant performance improvements with Promises in 10.x and probably even faster in 11.x, but we don't know until it is tested.
https://promisesaplus.com/
https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Promise
I just used it for copy. I think I can delete it.
https://nodejs.org/api/fs.html#fs_fs_copyfilesync_src_dest_flags
This library is incompatible with create-react-app since it uses UglifyJS2 in it's toolchain, which does not support the destructuring in imports.
When we try to build our app, we receive
Name expected [./~/aigle/lib/internal/collection.js:3,0][static/js/main.7201b8fd.js:151,6]
create-react-app is the official recommended bootstrap project to create React apps. It is recommended to make this library make this library compatible so we can reach more users.
I'm thinking to extend Aigle.parallel functionality as below,
(async () => {
const array1 = await Aigle.parallel([
(async () => 1)(),
(async () => 2)(),
(async () => 3)(),
]);
console.log(array1); // [1, 2, 3]
const array2 = await Aigle.parallel([
async () => 1,
async () => 2,
async () => 3,
]);
console.log(array2); // [[AsyncFunction], [AsyncFunction], [AsyncFunction]]
})();
// β
(async () => {
const array3 = await Aigle.parallel([
async () => 1,
async () => 2,
async () => 3,
]);
console.log(array3); // [1, 2, 3]
})();Also, I'll add Aigle.series and Aigle.parallelLimit which are smilar to async.series and async.parallelLimit.
1.2.0 to 1.2.1.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
husky is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 7 commits.
73c0ad7 1.2.1cb5fd3b Update CHANGELOG.mdc0e5f5e Update package-lock.jsonaabd390 Fix whitespace in project folder name issue (#423)d43f813 Update README.mdf0fcc21 Update README.md4897994 npm upgradeSee the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
I found that the aigle-es5.min.js in the npm package contains Object.assign even though it was only introduced with ES6/ES2015. Also, despite its min.js name, the file is not minified. Can you please look into these? Thank you!
Hi @suguru03,
Very nice library, I found this after looking for a good promise library, however I noticed that some control flow methods are missing from this library that are present in both async and neo-async, notably:
waterfall
queue
priorityQueue
cargo
Is there any plans to add these functions? These seem particularly useful and I would love to see them implemented if possible.
Thanks!
Q library implementation:
/**
* Turns an array of promises into a promise for an array of their states (as
* returned by `inspect`) when they have all settled.
* @param {Array[Any*]} values an array (or promise for an array) of values (or
* promises for values)
* @returns {Array[State]} an array of states for the respective values.
*/
Promise.prototype.allSettled = function () {
return this.then(function (promises) {
return all(array_map(promises, function (promise) {
promise = Q(promise);
function regardless() {
return promise.inspect();
}
return promise.then(regardless, regardless);
}));
});
};
I note that
aigle
.reduce(links, iterator, {})
.then(data => emitter.emit('end', data))resolve the promise in series. Is this intentional?
6.0.0 to 6.0.1.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The obligatory round of post-major-release bugfixes.
These issues were regressions.
test.js when run without arguments (@plroebuck)--ui (@boneskull)--watch (@boneskull)undefined value from a describe callback is no longer considered deprecated (@boneskull)@mocha/docdash@2 (@tendonstrength)The new version differs by 9 commits.
6d3d6b4 Release v6.0.12146ece update CHANGELOG.md for v6.0.17c9221d backout deprecation of value returned from suite; closes #3744b7cfceb fix --watch not finding any files to execute; closes #3748b836d73 Upgrade docdash version - issue #36637926f47 fix --ui issues, closes #374600f2ed9 dev dep upgrades from "npm audit" and "npm upgrade"34afb1a fix(cli/run.js): Revert default glob to match Mocha-5.26d5a0db Bring the example congfiguration file in line with the documentation. (#3751)See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
const _ = require('lodash');
const _$ = require('aigle')
$.mixin();
var main = (async function() {
const collection = [1, 4, 2];
var result1 = await _$.chain(collection).thru((e) => {
console.log('do aigle', e);
return e;
}).value();
console.log('aigle result', result1);
//do aigle 1
//do aigle 4
//do aigle 2
//aigle result 1
var result2 = await _.chain(collection).thru((e) => {
console.log('do lodash', e);
return e;
}).value();
console.log('lodash result', result2);
//do lodash [ 1, 4, 2 ]
//lodash result [ 1, 4, 2 ]
var result3 = await _$.chain(collection).then((e) => {
console.log('do aigle then', e);
return e;
}).value();
console.log('aigle then result', result3);
//do aigle then [ 1, 4, 2 ]
//aigle then result [ 1, 4, 2 ]
})()
8.1.4 to 8.1.5.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
lint-staged is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 2 commits.
63b085f fix: fix issue with scoped pkg listr-update-renderer (#587)1303573 docs: Update screencast and installation instructionsSee the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. πππ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google β€οΈ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.