Feature Stability

To have shared understanding of how stable a given feature is and how much can it be relied upon, this page lists available stability levels. It is heavily based on Node.js stability rankings.

Deprecated (0). This feature is known to be problematic, and changes or replacements are planned. Do not rely on it. Use of the feature may cause warnings. Backwards compatibility should not be expected.

Experimental (1). This feature may change or be removed in future versions. Please try it out and provide feedback. If it addresses a use-case that is important to you, tell us (create a discussion here).

Unstable (2). The API is in the process of settling, but has not yet had sufficient real-world testing to be considered stable. Backwards-compatibility will be maintained if reasonable.

Stable (3). The API has proven satisfactory, but cleanup in the underlying code may cause minor changes. Backwards-compatibility is guaranteed.

Mature (4). This API has been tested extensively in production and is unlikely to ever have to change. Unless serious bugs are found, this code will not ever change. Please do not suggest changes in this area, they will be refused.