From edc6a7af421defe9bb43e9a892d23e09987d7f9f Mon Sep 17 00:00:00 2001
From: Antoine du Hamel <duhamelantoine1995@gmail.com>
Date: Sun, 9 Jan 2022 12:42:38 +0100
Subject: [PATCH] doc: clarify `uncaughtException` `origin` for ESM

Fixes: https://github.com/nodejs/node/issues/41328

PR-URL: https://github.com/nodejs/node/pull/41339
Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com>
Reviewed-By: Bradley Farias <bradley.meck@gmail.com>
---
 doc/api/cli.md     |  3 +++
 doc/api/process.md | 16 ++++++++++------
 2 files changed, 13 insertions(+), 6 deletions(-)

diff --git a/doc/api/cli.md b/doc/api/cli.md
index 1c04da298b3760..63bd7aaa702609 100644
--- a/doc/api/cli.md
+++ b/doc/api/cli.md
@@ -1261,6 +1261,9 @@ occurs. One of the following modes can be chosen:
   set, trigger a warning, and set the process exit code to 1.
 * `none`: Silence all warnings.
 
+If a rejection happens during the command line entry point's ES module static
+loading phase, it will always raise it as an uncaught exception.
+
 ### `--use-bundled-ca`, `--use-openssl-ca`
 
 <!-- YAML
diff --git a/doc/api/process.md b/doc/api/process.md
index 1af45fe0240830..c222feefeef2a2 100644
--- a/doc/api/process.md
+++ b/doc/api/process.md
@@ -335,9 +335,11 @@ changes:
 * `err` {Error} The uncaught exception.
 * `origin` {string} Indicates if the exception originates from an unhandled
   rejection or from an synchronous error. Can either be `'uncaughtException'` or
-  `'unhandledRejection'`. The latter is only used in conjunction with the
-  [`--unhandled-rejections`][] flag set to `strict` or `throw` and
-  an unhandled rejection.
+  `'unhandledRejection'`. The latter is used when in an exception happens in a
+  `Promise` based async context (or if a `Promise` is rejected) and
+  [`--unhandled-rejections`][] flag set to `strict` or `throw` (which is the
+  default) and the rejection is not handled, or when a rejection happens during
+  the command line entry point's ES module static loading phase.
 
 The `'uncaughtException'` event is emitted when an uncaught JavaScript
 exception bubbles all the way back to the event loop. By default, Node.js
@@ -431,9 +433,11 @@ added:
 * `err` {Error} The uncaught exception.
 * `origin` {string} Indicates if the exception originates from an unhandled
   rejection or from synchronous errors. Can either be `'uncaughtException'` or
-  `'unhandledRejection'`. The latter is only used in conjunction with the
-  [`--unhandled-rejections`][] flag set to `strict` or `throw` and
-  an unhandled rejection.
+  `'unhandledRejection'`. The latter is used when in an exception happens in a
+  `Promise` based async context (or if a `Promise` is rejected) and
+  [`--unhandled-rejections`][] flag set to `strict` or `throw` (which is the
+  default) and the rejection is not handled, or when a rejection happens during
+  the command line entry point's ES module static loading phase.
 
 The `'uncaughtExceptionMonitor'` event is emitted before an
 `'uncaughtException'` event is emitted or a hook installed via