Skip to content

Commit 45156e1

Browse files
gireeshpunathilBethGriggs
authored andcommitted
doc: upgrade stability status of report API
The property `process.report.reportOnFatalError` was deemed experimental, as it was not honored under certain scenarios (for example out of memory conditions). The report configuration were previously stored on the `environment` structure which was not available on these types of fatal error cases. The referenced PR has addressed this case (sometime back), and the property is working as intended. Refs: #32207 PR-URL: #35654 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Beth Griggs <bgriggs@redhat.com>
1 parent 4348a35 commit 45156e1

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

doc/api/process.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1899,10 +1899,12 @@ Additional documentation is available in the [report documentation][].
18991899
### `process.report.reportOnFatalError`
19001900
<!-- YAML
19011901
added: v11.12.0
1902+
changes:
1903+
- version:
1904+
- REPLACEME
1905+
description: This API is no longer experimental.
19021906
-->
19031907

1904-
> Stability: 1 - Experimental
1905-
19061908
* {boolean}
19071909

19081910
If `true`, a diagnostic report is generated on fatal errors, such as out of

0 commit comments

Comments
 (0)