From e3594d5658effff6c2d8c6978944e433ac9ec549 Mon Sep 17 00:00:00 2001 From: Shubham Pandey Date: Fri, 8 Sep 2023 20:43:51 +0530 Subject: [PATCH] doc: update documentation for node:process warning PR-URL: https://github.com/nodejs/node/pull/49517 Refs: https://github.com/nodejs/node/issues/46862 Reviewed-By: Antoine du Hamel Reviewed-By: Moshe Atlow --- doc/api/process.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/api/process.md b/doc/api/process.md index a721faab321c60..5718c83e4fbcf4 100644 --- a/doc/api/process.md +++ b/doc/api/process.md @@ -606,7 +606,10 @@ process.on('warning', (warning) => { By default, Node.js will print process warnings to `stderr`. The `--no-warnings` command-line option can be used to suppress the default console output but the -`'warning'` event will still be emitted by the `process` object. +`'warning'` event will still be emitted by the `process` object. Currently, it +is not possible to suppress specific warning types other than deprecation +warnings. To suppress deprecation warnings, check out the [`--no-deprecation`][] +flag. The following example illustrates the warning that is printed to `stderr` when too many listeners have been added to an event: @@ -3954,6 +3957,7 @@ cases: [`'message'`]: child_process.md#event-message [`'uncaughtException'`]: #event-uncaughtexception [`--experimental-permission`]: cli.md#--experimental-permission +[`--no-deprecation`]: cli.md#--no-deprecation [`--unhandled-rejections`]: cli.md#--unhandled-rejectionsmode [`Buffer`]: buffer.md [`ChildProcess.disconnect()`]: child_process.md#subprocessdisconnect