Probably cool but needs examples/description in the readme/docs. Many projects make the mistake of thinking JSdoc for all their code is all the documentation they need. JSdoc usually just makes the codebase seem large and impenetrable, since there isn't a clear path to understanding wtf anything is in the context of the whole system.
It shouldn't matter what tech this is built on, but dogfooding is good for credibility. Also note that there's more WordPress branding on the site than JS, so the messaging feels totally off.
Yep, this really was a downer in ES5, but note that it's now a near a non-issue in ES6 with arrow functions:
```js
n.map(val => parseInt(val));
n.forEach(val => console.log(val))
async.waterfall([
next => new User(model).save(err => next(err)),
(data, next) => {
// MOAR CODE
}
])
```
Yep, this really was a downer in ES5, but note that it's now a near a non-issue in ES6 with arrow functions: ```js n.map(val => parseInt(val)); n.forEach(val => console.log(val)) async.waterfall([ next => new User(model).save(err => next(err)), (data, next) => { // MOAR CODE } ]) ```