Welcome to the official API reference documentation for Node.js!
\nNode.js is a JavaScript runtime built on the V8 JavaScript engine.
", "miscs": [ { "textRaw": "Contributing", "name": "contributing", "type": "misc", "desc": "Report errors in this documentation in the issue tracker. See\nthe contributing guide for directions on how to submit pull requests.
", "displayName": "Contributing" }, { "textRaw": "Stability index", "name": "Stability index", "type": "misc", "desc": "Throughout the documentation are indications of a section's stability. Some APIs\nare so proven and so relied upon that they are unlikely to ever change at all.\nOthers are brand new and experimental, or known to be hazardous.
\nThe stability indexes are as follows:
\n\n\nStability: 0 - Deprecated. The feature may emit warnings. Backward\ncompatibility is not guaranteed.
\n
\n\nStability: 1 - Experimental. The feature is not subject to\nsemantic versioning rules. Non-backward compatible changes or removal may\noccur in any future release. Use of the feature is not recommended in\nproduction environments.
\nExperimental features are subdivided into stages:
\n\n
\n- 1.0 - Early development. Experimental features at this stage are unfinished\nand subject to substantial change.
\n- 1.1 - Active development. Experimental features at this stage are nearing\nminimum viability.
\n- 1.2 - Release candidate. Experimental features at this stage are hopefully\nready to become stable. No further breaking changes are anticipated but may\nstill occur in response to user feedback or the features' underlying\nspecification development. We encourage user testing and feedback so that\nwe can know that this feature is ready to be marked as stable.
\nExperimental features leave the experimental status typically either by\ngraduating to stable, or are removed without a deprecation cycle.
\n
\n\nStability: 2 - Stable. Compatibility with the npm ecosystem is a high\npriority.
\n
\n\nStability: 3 - Legacy. Although this feature is unlikely to be removed and is\nstill covered by semantic versioning guarantees, it is no longer actively\nmaintained, and other alternatives are available.
\n
Features are marked as legacy rather than being deprecated if their use does no\nharm, and they are widely relied upon within the npm ecosystem. Bugs found in\nlegacy features are unlikely to be fixed.
\nUse caution when making use of Experimental features, particularly when\nauthoring libraries. Users may not be aware that experimental features are being\nused. Bugs or behavior changes may surprise users when Experimental API\nmodifications occur. To avoid surprises, use of an Experimental feature may need\na command-line flag. Experimental features may also emit a warning.
" }, { "textRaw": "Stability overview", "name": "stability_overview", "type": "misc", "displayName": "Stability overview" }, { "textRaw": "JSON output", "name": "json_output", "type": "misc", "meta": { "added": [ "v0.6.12" ], "changes": [] }, "desc": "Every .html document has a corresponding .json document. This is for IDEs\nand other utilities that consume the documentation.
Node.js functions which wrap a system call will document that. The docs link\nto the corresponding man pages which describe how the system call works.
\nMost Unix system calls have Windows analogues. Still, behavior differences may\nbe unavoidable.
", "displayName": "System calls and man pages" } ] } ] }