UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2916.0 Safari/537.36

Steps to reproduce the problem:
1. Follow Hello World example from https://expressjs.com/en/starter/hello-world.html

2. Add `Promise.reject()` in GET request.

3. Run and execute `curl http://localhost:3000`

Option 2 -

1. npm install bluebird.
2. add `require('bluebird').Promise.reject()`. This should also work.

What is the expected behavior?
Uncaught promise rejection is logged to console including full stack to match debugging web applications behavior.  Previously added in Chrome 40 see https://bugs.chromium.org/p/chromium/issues/detail?id=393913

What went wrong?
There is a node js warning but it doesn't print the promise call stack. 

Did this work before? N/A 

Chrome version: 56.0.2916.0  Channel: canary
OS Version: OS X 10.12.0
Flash Version: Shockwave Flash 24.0 r0