Not respecting `--unhandled-rejections=strict`

1. What version of bluebird is the issue happening on? 3.7.2

2. What platform and version? (For example Node.js 0.12 or Google Chrome 32) Node v14.5.0

Running following code:

setTimeout(() => console.log('not executed'), 1000)

const rejected = new Promise((res, rej) => {
  rej(new Error('error'))
})

with node’s native promise and cli option --unhandled-rejections=strict will terminate the script on unhandled rejection.

But when using Bluebirds promise, it will not.

const { Promise } = require('bluebird')

setTimeout(() => console.log('will be executed!'), 1000)

const rejected = new Promise((res, rej) => {
  rej(new Error('error'))
})

It seems that --unhandled-rejections=strict is ignored

[benjamingr]

9 out of 10 times the hard part is figuring out what to do and not the code change itself. The code change is trivial (just make strict use unhandledRejection) whereas figuring out if it’s worth the breaking change is definitely not clear cut.

Honestly I think it makes sense to delay this covnersation a few months in case the survey results indicate that strict will be the default anyway.

[misozask]

Thanks, I’m closing it.