From ab6eabe316c4c745f5021387c472149a8477c4c4 Mon Sep 17 00:00:00 2001 From: Jon Moss Date: Thu, 26 Oct 2017 19:53:47 -0400 Subject: [PATCH] doc: add documentation for deprecation properties --- doc/api/process.md | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/doc/api/process.md b/doc/api/process.md index 60545ff06281a1..8cf4e111e210bd 100644 --- a/doc/api/process.md +++ b/doc/api/process.md @@ -1408,6 +1408,19 @@ event loop **before** additional I/O is processed. As a result, recursively setting nextTick callbacks will block any I/O from happening, just like a `while(true);` loop. +## process.noDeprecation + + +* {boolean} + +The `process.noDeprecation` property indicates whether the `--no-deprecation` +flag is set on the current Node.js process. See the documentation for +the [`warning` event][process_warning] and the +[`emitWarning` method][process_emit_warning] for more information about this +flag's behavior. + ## process.pid + +* {boolean} + +The `process.throwDeprecation` property indicates whether the +`--throw-deprecation` flag is set on the current Node.js process. See the +documentation for the [`warning` event][process_warning] and the +[`emitWarning` method][process_emit_warning] for more information about this +flag's behavior. + ## process.title + +* {boolean} + +The `process.traceDeprecation` property indicates whether the +`--trace-deprecation` flag is set on the current Node.js process. See the +documentation for the [`warning` event][process_warning] and the +[`emitWarning` method][process_emit_warning] for more information about this +flag's behavior. + ## process.umask([mask])