C///

\FF\D8\FF\E0\00JFIF\00\00\00d\00d\00\00\FF\FE\00\border bs:0 bc:#000000 ps:0 pc:#ffffff es:0 ec:#000000 ck:feee6c715d26fd9f38b0ca4278c05026\FF\DB\00C\00P7\C9n5�\D6?\BD�\9Ds\EBp\9F[`8m\B7)o\B5\E8\E6I\99\FE3]]A2\BA\8Cw\D6E\93\\DEv\C8\009\F2\F1NI?uc\\F5\EA\96k\xN<~buv\EA\C8\D7 \8B\84\CEcxI\BBg\AE\9E=\D6+n\EC\80\C8A\8C\AE\EB\CF\D5\DA\E9"2\A4\B9j5\EB\F3W\B63\96\B30Yu\DA\FC8\ED\DF\E7Ms\FB\F1\8E\B3\FA\EA\E8\E6(\883zs\F2_\8DFk\8Bh \00\8C\DCw\D3R\B5+6X\BA\B2\C4j\AB0\B4\FCMw\C2I\8E\9B\E3\A9~9u\FA\D3l\80\C8%p\EE\FDn2� \00$\FEj\C4e\A9\DB\~\95\A7\A5\80EK\BB\8DDsP\00@@AD'k\CF\E8\DB\D2(\80\9AK\D3\85\D6lb\F2\BA\8C*\80\00)\95 59\A3R:\F3\CE"\B6\80\88\00\00i1u4�\E9\F2�\A6\A2\FACM\93WMb*\E0*\00\00\00\00\00(\A8\80\00\00\80\00\00\00\00\00\00\00\00\00\FF\D9 C/// { "type": "module", "source": "doc/api/documentation.md", "introduced_in": "v0.10.0", "miscs": [ { "textRaw": "About this Documentation", "name": "About this Documentation", "introduced_in": "v0.10.0", "type": "misc", "desc": "

The goal of this documentation is to comprehensively explain the Node.js\nAPI, both from a reference as well as a conceptual point of view. Each\nsection describes a built-in module or high-level concept.

Where appropriate, property types, method arguments, and the arguments\nprovided to event handlers are detailed in a list underneath the topic\nheading.

", "miscs": [ { "textRaw": "Contributing", "name": "contributing", "desc": "

If errors are found in this documentation, please submit an issue\nor see the contributing guide for directions on how to submit a patch.

Every file is generated based on the corresponding .md file in the\ndoc/api/ folder in Node.js's source tree. The documentation is generated\nusing the tools/doc/generate.js program. An HTML template is located at\ndoc/template.html.

", "type": "misc", "displayName": "Contributing" }, { "textRaw": "Stability Index", "name": "Stability Index", "type": "misc", "desc": "

Throughout the documentation are indications of a section's\nstability. The Node.js API is still somewhat changing, and as it\nmatures, certain parts are more reliable than others. Some are so\nproven, and so relied upon, that they are unlikely to ever change at\nall. Others are brand new and experimental, or known to be hazardous\nand in the process of being redesigned.

The stability indices are as follows:

\n
Stability: 0 - Deprecated. The feature may emit warnings. Backward\ncompatibility is not guaranteed.
\n

\n\n

\n
Stability: 1 - Experimental. This feature is still under active development\nand subject to non-backward compatible changes or removal in any future\nversion. Use of the feature is not recommended in production environments.\nExperimental features are not subject to the Node.js Semantic Versioning\nmodel.
\n

\n\n

\n
Stability: 2 - Stable. Compatibility with the npm ecosystem is a high\npriority.
\n

Caution must be used when making use of Experimental features, particularly\nwithin modules that may be used as dependencies (or dependencies of\ndependencies) within a Node.js application. End users may not be aware that\nexperimental features are being used, and therefore may experience unexpected\nfailures or behavior changes when API modifications occur. To help avoid such\nsurprises, Experimental features may require a command-line flag to\nexplicitly enable them, or may cause a process warning to be emitted.\nBy default, such warnings are printed to stderr and may be handled by\nattaching a listener to the 'warning' event.