Skip to content

Commit

Permalink
doc: add documentation for deprecation properties
Browse files Browse the repository at this point in the history
PR-URL: #16539
Fixes: #16394
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
  • Loading branch information
maclover7 committed Jan 13, 2018
1 parent 1385e1b commit c770f43
Showing 1 changed file with 39 additions and 0 deletions.
39 changes: 39 additions & 0 deletions doc/api/process.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
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
Expand Down Expand Up @@ -1778,6 +1791,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
Expand All @@ -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
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
Expand Down

0 comments on commit c770f43

Please sign in to comment.