1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: add documentation for deprecation properties

Browse Source 
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>
This commit is contained in:
Jon Moss 2017-10-26 19:53:47 -04:00
parent 1385e1bc63
commit c770f43a91
1 changed files with 39 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
doc/api/process.md
View File

@ -1405,6 +1405,19 @@ event loop **before** additional I/O is processed. As a result,
recursively setting nextTick callbacks will block any I/O from recursively setting nextTick callbacks will block any I/O from
happening, just like a `while(true);` loop. 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 ## process.pid
<!-- YAML <!-- YAML
added: v0.1.15 added: v0.1.15
@ -1778,6 +1791,19 @@ false
See the [TTY][] documentation for more information. 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 ## process.title
<!-- YAML <!-- YAML
added: v0.1.104 added: v0.1.104
@ -1798,6 +1824,19 @@ process. Node.js v0.8 allowed for longer process title strings by also
overwriting the `environ` memory but that was potentially insecure and overwriting the `environ` memory but that was potentially insecure and
confusing in some (rather obscure) cases. 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]) ## process.umask([mask])
<!-- YAML <!-- YAML
added: v0.1.19 added: v0.1.19