Skip to content

Commit 8cb3c20

Browse files
RafaelGSSruyadorno
authored andcommitted
doc: sort --report-exclude alphabetically
PR-URL: #55788 Backport-PR-URL: #56055 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Ulises Gascón <ulisesgascongonzalez@gmail.com> PR-URL: #55697
1 parent 2e3ca1b commit 8cb3c20

File tree

1 file changed

+20
-9
lines changed

1 file changed

+20
-9
lines changed

doc/api/cli.md

+20-9
Original file line numberDiff line numberDiff line change
@@ -1985,6 +1985,26 @@ changes:
19851985

19861986
Location at which the report will be generated.
19871987

1988+
### `--report-exclude-env`
1989+
1990+
<!-- YAML
1991+
added: REPLACEME
1992+
-->
1993+
1994+
When `--report-exclude-env` is passed the diagnostic report generated will not
1995+
contain the `environmentVariables` data.
1996+
1997+
### `--report-exclude-network`
1998+
1999+
<!-- YAML
2000+
added:
2001+
- v22.0.0
2002+
- v20.13.0
2003+
-->
2004+
2005+
Exclude `header.networkInterfaces` from the diagnostic report. By default
2006+
this is not set and the network interfaces are included.
2007+
19882008
### `--report-filename=filename`
19892009

19902010
<!-- YAML
@@ -2049,15 +2069,6 @@ Enables report to be generated upon receiving the specified (or predefined)
20492069
signal to the running Node.js process. The signal to trigger the report is
20502070
specified through `--report-signal`.
20512071

2052-
### `--report-exclude-env`
2053-
2054-
<!-- YAML
2055-
added: REPLACEME
2056-
-->
2057-
2058-
When `--report-exclude-env` is passed the diagnostic report generated will not
2059-
contain the `environmentVariables` data.
2060-
20612072
### `--report-signal=signal`
20622073

20632074
<!-- YAML

0 commit comments

Comments
 (0)