Node v7.5.0 Released

Post by chadscira » Fri, Feb 03, 2017, 4:21 PM UTC

nailer wrote: post #56

Bahamut wrote: post #36

Earlier quoted context omitted.

I highly recommend against using that library - it encourages a lot of callback hell we've found at my company, and it is much harder to create nice reusable functions with it vs. promises. bluebird is a wholly superior library for handling async flow.

> it encourages a lot of callback hell we've found at my company This is a very odd comment. async provides the same level of indentation as Promises does: async.waterfall([ function(){}, function(){}, ]) Here's promises doing the same thing: function() .then(function(){}) .then(function(){}) One's a list of functions to be run in order, the other uses method chaining. You may prefer one or the other but saying async…

    await asyncFuncOne();
    await asyncFuncTwo();

Post by rhinoceraptor » Fri, Feb 03, 2017, 4:24 PM UTC

thealfreds wrote: post #55

zachrose wrote: post #45

Earlier quoted context omitted.

So much of the promise-based code I see looks almost the same as it would with plain callbacks, just with the callbacks plopped into .then(). Am I missing something? How do promises make for more reusable functions?

Chaining and returning can keep things nice and neat. Say you are following a Controller -> Service -> Repo implementation. Controller calls the service. Service returns a call to a repo with any mapping that needs to occur. Repo calls out to database or external api and returns the promise. Makes the work very boring and repetitive for the most part which is a good thing I think. function someController(req, res) {…

Post by randallsquared » Fri, Feb 03, 2017, 4:47 PM UTC

gsathya_hn wrote: post #88

GeneralMaximus wrote: post #30

Earlier quoted context omitted.

Automatic promisification and the disposer pattern are both Bluebird-specific features that native ES6 promises don't support, so you'll have to continue using Bluebird if you rely on them. However, promises returned by Promises/A+ compliant libraries -- and this includes native ES6 promises -- are interoperable with each other. That means you can mix Bluebird promises with native promises for the most part . E.g, pa…

Native promises and bluebird use different microtask queues on Node which makes interop incorrect (which is also one of the reasons why bluebird is ES6 spec non compliant). See https://gist.github.com/anonymous/9936c695f2c29e79a0c1a0dec8... This might lead to subtle ordering bugs, I would recommend against using both together. Using bluebird and native promises together may result in slower performance because V8 has…

Post by thealfreds » Fri, Feb 03, 2017, 4:53 PM UTC

rhinoceraptor wrote: post #93

thealfreds wrote: post #55

Earlier quoted context omitted.

Chaining and returning can keep things nice and neat. Say you are following a Controller -> Service -> Repo implementation. Controller calls the service. Service returns a call to a repo with any mapping that needs to occur. Repo calls out to database or external api and returns the promise. Makes the work very boring and repetitive for the most part which is a good thing I think. function someController(req, res) {…

It's trivial to refactor that code to use only callbacks, without ending up with callback hell. You certainly want to call UserService.getUser for many different controllers. Why manually do that for each controller? Simply make a middleware to get the user. If you take this to its logical conclusion, you end up with small, composable middleware functions, and controllers that are pure functions.

Post by level » Fri, Feb 03, 2017, 5:00 PM UTC

imrehg wrote: post #34

k__ wrote: post #28

Earlier quoted context omitted.

I don't understand

"AWS Lambda supports the following runtime versions: Node.js – v4.3.2" http://docs.aws.amazon.com/lambda/latest/dg/current-supporte...