Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc: update documentation for --no-warnings #47031

Closed
wants to merge 1 commit into from
Closed

doc: update documentation for --no-warnings #47031

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion doc/api/process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`
Comment on lines +610 to +611
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
it is not supported to supress specific warning types like `ExperimentalWarning`.
To supress deprecation warnings please lookat `--no-deprecation`
it is not supported to suppress specific warning types like `ExperimentalWarning`.
To suppress deprecation warnings please look at the `--no-deprecation`

command-line flag as below.
Comment on lines +611 to +612
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's have a link so users don't have to look for it.

Suggested change
To supress deprecation warnings please lookat `--no-deprecation`
command-line flag as below.
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:
Expand Down