News for hackers. Stuff that matters.
Re:Node v6.6.0 by danneu on Thursday September 15, 2016 @06:55PM (#12510547)
This will save a lot of time across the Node ecosystem.

Forgetting to handle rejection is probably the most common error I see when people post Promise snippets in #node.js. Silent failure is so deadly. "Why do my requests hang?"

Re:Node v6.6.0 by jamesrom on Thursday September 15, 2016 @08:28PM (#12511054)
Sometimes you just want an error to bubble up and be caught above. There's absolutely no reason to catch every rejection in the scope where the promise was created.
Re:Node v6.6.0 by danneu on Thursday September 15, 2016 @08:59PM (#12511189)
Yeah, looks like it just checks on nextTick, so it only warns when you don't attach a handler synchronously. Versus warning only if it's unreachable (like on garbage collection).

Though it does emit another message when rejection is handled asynchronously.

    > var p = new Promise((_, reject) => reject('lol')) \
      setTimeout(() => p.catch(() => console.log('handled')), 0)
    UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 5): lol
    PromiseRejectionHandledWarning: Rejection handled asynchronously (rejection id: 5)
Consolation prize?

Fortunately, most of the run of the mill promises I can think of off the top of my head get rejection handlers attached synchronously, like in upstream middleware. I might be drawing a blank, though.