This post was contributed by the Node.js Technical Steering Committee.
The Node.js Project, an impact project of the OpenJS Foundation, handles unhandled rejections by emitting a deprecation warning to stderr. The warning shows the stack where the rejection happened, and states that in future Node.js versions unhandled rejections will result in Node.js exiting with non-zero status code. We intend to remove the deprecation warning, replacing it with a stable behavior which might be different from the one described on the deprecation warning. We’re running a survey to better understand how Node.js users are using Promises and how they are dealing with unhandled rejections today, so we can make an informed decision on how to move forward.
To learn more about what unhandled rejections are and potential issues with it, check out the original post. Those interested in helping the TSC solve this are encouraged to participate in the survey, which will close on August 24th.