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

doc: order deprecation reasons

Browse Source 
PR-URL: https://github.com/nodejs/node/pull/27960
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com>
This commit is contained in:
Trivikram Kamat 2019-05-29 15:57:26 -07:00
parent 965ffc4cb9
commit 5c61c5d152
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/api/deprecations.md
View File

@ -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 for any of the following reasons:
* 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.
Node.js utilizes three kinds of Deprecations: