diff options
| author | Jon Moss <me@jonathanmoss.me> | 2017-10-27 02:53:47 +0300 |
|---|---|---|
| committer | Myles Borins <mylesborins@google.com> | 2018-02-27 08:38:13 +0300 |
| commit | 5607f587b22ebf3ed0cd0f112ed0cdff25d06a05 (patch) | |
| tree | 5efb60e07edd13129aa4b20cc64821540d300449 | |
| parent | 98579decd7ca55d2d4db56d81c8bd780b61d5b60 (diff) | |
doc: add documentation for deprecation properties
PR-URL: https://github.com/nodejs/node/pull/16539
Fixes: https://github.com/nodejs/node/issues/16394
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
| -rw-r--r-- | doc/api/process.md | 39 |
1 files changed, 39 insertions, 0 deletions
diff --git a/doc/api/process.md b/doc/api/process.md index 48f3f9a73cb..ce1c6161fed 100644 --- a/doc/api/process.md +++ b/doc/api/process.md @@ -1342,6 +1342,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 +<!-- YAML +added: v0.8.0 +--> + +* {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 <!-- YAML added: v0.1.15 @@ -1692,6 +1705,19 @@ false See the [TTY][] documentation for more information. +## process.throwDeprecation +<!-- YAML +added: v0.9.12 +--> + +* {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 <!-- YAML added: v0.1.104 @@ -1712,6 +1738,19 @@ process. Node.js v0.8 allowed for longer process title strings by also overwriting the `environ` memory but that was potentially insecure and confusing in some (rather obscure) cases. +## process.traceDeprecation +<!-- YAML +added: v0.8.0 +--> + +* {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]) <!-- YAML added: v0.1.19 |