Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 9dd4813

Browse filesBrowse files
trivikrBridgeAR
authored andcommitted
doc: order deprecation reasons
PR-URL: #27960 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com>
1 parent 62de36e commit 9dd4813
Copy full SHA for 9dd4813

File tree

Expand file treeCollapse file tree

1 file changed

+5
-3
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

1 file changed

+5
-3
lines changed
Open diff view settings
Collapse file

‎doc/api/deprecations.md‎

Copy file name to clipboardExpand all lines: doc/api/deprecations.md
+5-3Lines changed: 5 additions & 3 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,11 @@
33
<!--introduced_in=v7.7.0-->
44
<!-- type=misc -->
55

6-
Node.js may deprecate APIs when either: (a) use of the API is considered to be
7-
unsafe, (b) an improved alternative API is available, or (c) breaking changes to
8-
the API are expected in a future major release.
6+
Node.js may deprecate APIs for any of the following reasons:
7+
8+
* Use of the API is considered to be unsafe.
9+
* An improved alternative API is available.
10+
* Breaking changes to the API are expected in a future major release.
911

1012
Node.js utilizes three kinds of Deprecations:
1113

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.