From cef3b739dcebbfa55fe3fb57837448f494b67bfa Mon Sep 17 00:00:00 2001 From: Jagadeesh Meesala Date: Thu, 9 Mar 2023 23:11:02 -0500 Subject: [PATCH] doc: update documentation for --no-warnings updated documentation for --no-warnings command-line option. Refs:https://github.com/nodejs/node/issues/30810 --- doc/api/process.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/api/process.md b/doc/api/process.md index e9ef0a972de01c..dfc27d55ab370b 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. At this point, +it is not supported to supress specific warning types like `ExperimentalWarning`. +To supress deprecation warnings please lookat `--no-deprecation` +command-line flag as below. The following example illustrates the warning that is printed to `stderr` when too many listeners have been added to an event: