Skip to content

Commit 730e25d

Browse files
cjihrigtargos
authored andcommitted
doc: add unhandledRejection to strict mode
`lib/internal/process/promises.js` contains the following comment about --unhandled-rejections=strict. This commit updates the docs to reflect this: // --unhandled-rejections=strict: // Emit 'uncaughtException'. If it's not handled, print // the error to stderr and exit the process. // Otherwise, emit 'unhandledRejection'. If // 'unhandledRejection' is not // handled, emit 'UnhandledPromiseRejectionWarning'. Fixes: #41184 PR-URL: #41194 Reviewed-By: Derek Lewis <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
1 parent aa7d147 commit 730e25d

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

doc/api/cli.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -1254,7 +1254,8 @@ occurs. One of the following modes can be chosen:
12541254

12551255
* `throw`: Emit [`unhandledRejection`][]. If this hook is not set, raise the
12561256
unhandled rejection as an uncaught exception. This is the default.
1257-
* `strict`: Raise the unhandled rejection as an uncaught exception.
1257+
* `strict`: Raise the unhandled rejection as an uncaught exception. If the
1258+
exception is handled, [`unhandledRejection`][] is emitted.
12581259
* `warn`: Always trigger a warning, no matter if the [`unhandledRejection`][]
12591260
hook is set or not but do not print the deprecation warning.
12601261
* `warn-with-error-code`: Emit [`unhandledRejection`][]. If this hook is not

0 commit comments

Comments
 (0)