Make sure exit code is zero on unhandled promise rejection in node #182
Comments
|
+1, although @arichiardi I think you mean "non-zero", correct? We got hit by this. Builds were passing in Jenkins despite the tests actually failing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello @bensu and all!
I know this is controversial and I can handle it myself in my side of the code but I was wondering whether it makes sense to adopt the following solution by default for
:nodetargets in case of unhandled promise rejection.https://medium.com/@dtinth/making-unhandled-promise-rejections-crash-the-node-js-process-ffc27cfcc9dd
Leaving this here for further discussion.
The text was updated successfully, but these errors were encountered: