doc: abort controller emits error in child process
Fixes: https://github.com/nodejs/node/issues/46036 PR-URL: https://github.com/nodejs/node/pull/46072 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
This commit is contained in:
parent
57add38bd3
commit
40815df683
@ -1186,9 +1186,10 @@ property is `false`.
|
||||
|
||||
The `'error'` event is emitted whenever:
|
||||
|
||||
1. The process could not be spawned, or
|
||||
2. The process could not be killed, or
|
||||
3. Sending a message to the child process failed.
|
||||
* The process could not be spawned.
|
||||
* The process could not be killed.
|
||||
* Sending a message to the child process failed.
|
||||
* The child process was aborted via the `signal` option.
|
||||
|
||||
The `'exit'` event may or may not fire after an error has occurred. When
|
||||
listening to both the `'exit'` and `'error'` events, guard
|
||||
|
Loading…
x
Reference in New Issue
Block a user