3
3
<!-- type=misc -->
4
4
5
5
The goal of this documentation is to comprehensively explain the Node.js
6
- API, both from a reference as well as a conceptual point of view. Each
6
+ API, both from a reference as well as a conceptual point of view. Each
7
7
section describes a built-in module or high-level concept.
8
8
9
9
Where appropriate, property types, method arguments, and the arguments
10
10
provided to event handlers are detailed in a list underneath the topic
11
11
heading.
12
12
13
13
Every ` .html ` document has a corresponding ` .json ` document presenting
14
- the same information in a structured manner. This feature is
14
+ the same information in a structured manner. This feature is
15
15
experimental, and added for the benefit of IDEs and other utilities that
16
16
wish to do programmatic things with the documentation.
17
17
18
18
Every ` .html ` and ` .json ` file is generated based on the corresponding
19
- ` .md ` file in the ` doc/api/ ` folder in Node.js's source tree. The
19
+ ` .md ` file in the ` doc/api/ ` folder in Node.js's source tree. The
20
20
documentation is generated using the ` tools/doc/generate.js ` program.
21
21
The HTML template is located at ` doc/template.html ` .
22
22
@@ -39,17 +39,29 @@ The stability indices are as follows:
39
39
40
40
``` txt
41
41
Stability: 0 - Deprecated
42
- This feature is known to be problematic, and changes are
43
- planned. Do not rely on it. Use of the feature may cause warnings. Backwards
44
- compatibility should not be expected.
42
+ This feature is known to be problematic, and changes may be planned. Do
43
+ not rely on it. Use of the feature may cause warnings to be emitted.
44
+ Backwards compatibility across major versions should not be expected.
45
45
```
46
46
47
47
``` txt
48
48
Stability: 1 - Experimental
49
- This feature is subject to change, and is gated by a command line flag.
50
- It may change or be removed in future versions.
49
+ This feature is still under active development and subject to non-backwards
50
+ compatible changes, or even removal, in any future version. Use of the feature
51
+ is not recommended in production environments. Experimental features are not
52
+ subject to the Node.js Semantic Versioning model.
51
53
```
52
54
55
+ * Note* : Caution must be used when making use of ` Experimental ` features,
56
+ particularly within modules that may be used as dependencies (or dependencies
57
+ of dependencies) within a Node.js application. End users may not be aware that
58
+ experimental features are being used, and therefore may experience unexpected
59
+ failures or behavioral changes when changes occur. To help avoid such surprises,
60
+ ` Experimental ` features may require a command-line flag to explicitly enable
61
+ them, or may cause a process warning to be emitted. By default, such warnings
62
+ are printed to ` stderr ` and may be handled by attaching a listener to the
63
+ ` process.on('warning') ` event.
64
+
53
65
``` txt
54
66
Stability: 2 - Stable
55
67
The API has proven satisfactory. Compatibility with the npm ecosystem
@@ -63,7 +75,7 @@ is a high priority, and will not be broken unless absolutely necessary.
63
75
Every HTML file in the markdown has a corresponding JSON file with the
64
76
same data.
65
77
66
- This feature was added in Node.js v0.6.12. It is experimental.
78
+ This feature was added in Node.js v0.6.12. It is experimental.
67
79
68
80
## Syscalls and man pages
69
81
@@ -72,7 +84,7 @@ and the underlying operating system. Node functions which simply wrap a syscall,
72
84
like ` fs.open() ` , will document that. The docs link to the corresponding man
73
85
pages (short for manual pages) which describe how the syscalls work.
74
86
75
- ** Caveat :** some syscalls, like lchown(2), are BSD-specific. That means, for
87
+ ** Note :** some syscalls, like lchown(2), are BSD-specific. That means, for
76
88
example, that ` fs.lchown() ` only works on macOS and other BSD-derived systems,
77
89
and is not available on Linux.
78
90
0 commit comments