On this page

About this documentation

History

Welcome to the official API reference documentation for Node.js!

Node.js is a JavaScript runtime built on the V8 JavaScript engine.

Report errors in this documentation in the issue tracker. See the contributing guide for directions on how to submit pull requests.

Throughout the documentation are indications of a section's stability. Some APIs are so proven and so relied upon that they are unlikely to ever change at all. Others are brand new and experimental, or known to be hazardous.

The stability indexes are as follows:

Stability: 0Deprecated. The feature may emit warnings. Backward compatibility is not guaranteed.
Stability: 1Experimental. The feature is not subject to semantic versioning rules. Non-backward compatible changes or removal may occur in any future release. Use of the feature is not recommended in production environments.
Stability: 2Stable. Compatibility with the npm ecosystem is a high priority.
Stability: 3Legacy. Although this feature is unlikely to be removed and is still covered by semantic versioning guarantees, it is no longer actively maintained, and other alternatives are available.

Features are marked as legacy rather than being deprecated if their use does no harm, and they are widely relied upon within the npm ecosystem. Bugs found in legacy features are unlikely to be fixed.

Use caution when making use of Experimental features, particularly when authoring libraries. Users may not be aware that experimental features are being used. Bugs or behavior changes may surprise users when Experimental API modifications occur. To avoid surprises, use of an Experimental feature may need a command-line flag. Experimental features may also emit a warning.

APIStability
Assert2Stable
Async hooks1Experimental
Asynchronous context tracking2Stable
Buffer2Stable
Child process2Stable
Cluster2Stable
Console2Stable
Crypto2Stable
Debugger2Stable
Diagnostic report2Stable
Diagnostics Channel2Stable
DNS2Stable
Domain0Deprecated
Events2Stable
File system2Stable
Global objects2Stable
HTTP2Stable
HTTP/22Stable
HTTPS2Stable
Inspector2Stable
Modules: CommonJS modules2Stable
Modules: ECMAScript modules2Stable
Modules: TypeScript2Stable
Net2Stable
Node-API2Stable
OS2Stable
Path2Stable
Performance measurement APIs2Stable
Punycode0Deprecated
Query string2Stable
QUIC1Early development
Readline2Stable
REPL2Stable
Single executable applications1Active development
SQLite1Release candidate.
Stream2Stable
String decoder2Stable
Test runner2Stable
Timers2Stable
TLS (SSL)2Stable
Trace events1Experimental
TTY2Stable
UDP/datagram sockets2Stable
URL2Stable
Util2Stable
VM (executing JavaScript)2Stable
Web Crypto API2Stable
Web Streams API2Stable
WebAssembly System Interface (WASI)1Experimental
Worker threads2Stable
Zlib2Stable

JSON output

History

Every .html document has a corresponding .json document. This is for IDEs and other utilities that consume the documentation.

Node.js functions which wrap a system call will document that. The docs link to the corresponding man pages which describe how the system call works.

Most Unix system calls have Windows analogues. Still, behavior differences may be unavoidable.