From c3f6a154672807f1c1c433c6b098477dbd57e143 Mon Sep 17 00:00:00 2001 From: "trop[bot]" <37223003+trop[bot]@users.noreply.github.com> Date: Tue, 27 Jan 2026 11:34:36 +0100 Subject: [PATCH] docs: correct type for `process.noDeprecation` (#49546) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * docs: correct type for process.noDeprecation Co-authored-by: Shelley Vohr * docs: mark `noDeprecation` as optional instead Co-authored-by: René Co-authored-by: David Sanders --------- Co-authored-by: trop[bot] <37223003+trop[bot]@users.noreply.github.com> Co-authored-by: Shelley Vohr Co-authored-by: David Sanders --- docs/api/process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api/process.md b/docs/api/process.md index 91e42942ff..78685084d2 100644 --- a/docs/api/process.md +++ b/docs/api/process.md @@ -71,7 +71,7 @@ will disable the support for `asar` archives in Node's built-in modules. ### `process.noDeprecation` -A `boolean` that controls whether or not deprecation warnings are printed to `stderr`. +A `boolean` (optional) that controls whether or not deprecation warnings are printed to `stderr`. Setting this to `true` will silence deprecation warnings. This property is used instead of the `--no-deprecation` command line flag.