News for hackers. Stuff that matters.
Re:Node v8.0.0 Released by NoInkling on Wednesday May 31, 2017 @02:33AM (#14450751)
Previously that characteristic was also a massive pain point for debugging Node apps though - neglecting error handling would result in silently swallowed errors and leave people (particularly newbies) scratching their heads.

Then they added unhandled rejection warnings by default, and all was ok again - but I see why someone might insist that all examples have error handling.

Re:Node v8.0.0 Released by minitech on Wednesday May 31, 2017 @10:56PM (#14457663)
That’s not something that should be handled inside an async function (and therefore not in this example). If you don’t want to continue a promise chain, terminate it:

  .catch(error => {
    process.nextTick(() => { throw error; });
  })
Re:Node v8.0.0 Released by partycoder on Thursday June 01, 2017 @01:22AM (#14458181)
You want to use setImmediate rather than process.nextTick.
Re:Node v8.0.0 Released by minitech on Thursday June 01, 2017 @09:37PM (#14466782)
Mmm… no, I didn’t want to. Why do you say that?