GeezerVison is showing github.com — doc: update documentation for node:process warning · nodejs/node@e3594d5
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: doc/api/process.md +5-1Lines changed: 5 additions & 1 deletion - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -606,7 +606,10 @@ process.on('warning', (warning) => { |
606 | 606 |
|
607 | 607 | By default, Node.js will print process warnings to `stderr`. The `--no-warnings` |
608 | 608 | command-line option can be used to suppress the default console output but the |
609 | | -`'warning'` event will still be emitted by the `process` object. |
| 609 | +`'warning'` event will still be emitted by the `process` object. Currently, it |
| 610 | +is not possible to suppress specific warning types other than deprecation |
| 611 | +warnings. To suppress deprecation warnings, check out the [`--no-deprecation`][] |
| 612 | +flag. |
610 | 613 |
|
611 | 614 | The following example illustrates the warning that is printed to `stderr` when |
612 | 615 | too many listeners have been added to an event: |
@@ -3954,6 +3957,7 @@ cases: |
3954 | 3957 | [`'message'`]: child_process.md#event-message |
3955 | 3958 | [`'uncaughtException'`]: #event-uncaughtexception |
3956 | 3959 | [`--experimental-permission`]: cli.md#--experimental-permission |
| 3960 | +[`--no-deprecation`]: cli.md#--no-deprecation |
3957 | 3961 | [`--unhandled-rejections`]: cli.md#--unhandled-rejectionsmode |
3958 | 3962 | [`Buffer`]: buffer.md |
3959 | 3963 | [`ChildProcess.disconnect()`]: child_process.md#subprocessdisconnect |
|