Skip to content

docs: fixup alignment of warning subsection #51374

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

Merged
nodejs-github-bot merged 1 commit into from
Jan 5, 2024
Merged

docs: fixup alignment of warning subsection #51374

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
24 changes: 12 additions & 12 deletions doc/api/process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -650,18 +650,6 @@ of the custom deprecation.
The `*-deprecation` command-line flags only affect warnings that use the name
`'DeprecationWarning'`.

### Event: `'worker'`

<!-- YAML
added:
- v16.2.0
- v14.18.0
-->

* `worker` {Worker} The {Worker} that was created.

The `'worker'` event is emitted after a new {Worker} thread has been created.

#### Emitting custom warnings

See the [`process.emitWarning()`][process_emit_warning] method for issuing
Expand Down Expand Up @@ -690,6 +678,18 @@ A few of the warning types that are most common include:
that will be ignored rather than treated as an error. One example is use of
the HTTP response status message when using the HTTP/2 compatibility API.

### Event: `'worker'`

<!-- YAML
added:
- v16.2.0
- v14.18.0
-->

* `worker` {Worker} The {Worker} that was created.

The `'worker'` event is emitted after a new {Worker} thread has been created.

### Signal events

<!--type=event-->
Expand Down