Skip to content
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
doc: order deprecation reasons
  • Loading branch information
trivikr committed Jun 3, 2019
commit 05f668b98ed64c77e86f7b22c9c49c94b56b8b9b
8 changes: 5 additions & 3 deletions doc/api/deprecations.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,11 @@
<!--introduced_in=v7.7.0-->
<!-- type=misc -->

Node.js may deprecate APIs when either: (a) use of the API is considered to be
unsafe, (b) an improved alternative API is available, or (c) breaking changes to
the API are expected in a future major release.
Node.js may deprecate APIs in the following cases:
Comment thread
trivikr marked this conversation as resolved.
Outdated

* use of the API is considered to be unsafe
* an improved alternative API is available
* breaking changes to the API are expected in a future major release.
Comment thread
trivikr marked this conversation as resolved.
Outdated

Node.js utilizes three kinds of Deprecations:

Expand Down