@@ -32,6 +32,18 @@ The stability indices are as follows:
32
32
> [ semantic versioning] [ ] rules. Non-backward compatible changes or removal may
33
33
> occur in any future release. Use of the feature is not recommended in
34
34
> production environments.
35
+ >
36
+ > Experimental features are subdivided into stages:
37
+ >
38
+ > * 1.0 - Early development. Experimental features at this stage are unfinished
39
+ > and subject to substantial change.
40
+ > * 1.1 - Active development. Experimental features at this stage are nearing
41
+ > minimum viability.
42
+ > * 1.2 - Release candidate. Experimental features at this stage are hopefully
43
+ > ready to become stable. No further breaking changes are anticipated but may
44
+ > still occur in response to user feedback. We encourage user testing and
45
+ > feedback so that we can know that this feature is ready to be marked as
46
+ > stable.
35
47
36
48
<!-- separator -->
37
49
@@ -48,9 +60,9 @@ Features are marked as legacy rather than being deprecated if their use does no
48
60
harm, and they are widely relied upon within the npm ecosystem. Bugs found in
49
61
legacy features are unlikely to be fixed.
50
62
51
- Use caution when making use of Experimental features, particularly within
52
- modules . Users may not be aware that experimental features are being used.
53
- Bugs or behavior changes may surprise users when Experimental API
63
+ Use caution when making use of Experimental features, particularly when
64
+ authoring libraries . Users may not be aware that experimental features are being
65
+ used. Bugs or behavior changes may surprise users when Experimental API
54
66
modifications occur. To avoid surprises, use of an Experimental feature may need
55
67
a command-line flag. Experimental features may also emit a [ warning] [ ] .
56
68
0 commit comments