https://nodejs.org/en/docs/
-
API reference documentation
The API reference documentation provides detailed information about a function or object in Node.js. This documentation indicates what arguments a method accepts, the return value of that method, and what errors may be related to that method. It also indicates which methods are available for different versions of Node.js.
-
ES6 features
The ES6 section describes the three ES6 feature groups , and details which features are enabled by default in Node.js, alongside explanatory links. It also shows how to find which version of V8 shipped with a particular Node.js release.
-
Guides
The Guides section has long-form, in-depth articles about Node.js technical features and capabilities.
-
Dependencies
libraries and tools
Node.js v15.14.0 documentation(面试会考)
- Assertion testing
- Async hooks
- Buffer
- C++ addons
- C/C++ addons with Node-API
- C++ embedder API
- Child processes
- Cluster
- Command-line options
- Console
- Crypto
- Debugger
- Deprecated APIs
- Diagnostics Channel
- DNS
- Domain
- Errors
- Events
- File system
- Globals
- HTTP
- HTTP/2
- HTTPS
- Inspector
- Internationalization
- Modules: CommonJS modules
- Modules: ECMAScript modules
- Modules:
module
API - Modules: Packages
- Net
- OS
- Path
- Performance hooks
- Policies
- Process
- Punycode
- Query strings
- Readline
- REPL
- Report
- Stream
- String decoder
- Timers
- TLS/SSL
- Trace events
- TTY
- UDP/datagram
- URL
- Utilities
- V8
- VM
- WASI
- Web Crypto API
- Worker threads
- ZlibCode repository and issue tracker
Node.js is built against modern versions of V8. By keeping up-to-date with the latest releases of this engine, we ensure new features from the JavaScript ECMA-262 specification are brought to Node.js developers in a timely manner, as well as continued performance and stability improvements.
All ECMAScript 2015 (ES6) features are split into three groups for shipping, staged, and in progress features:
- All shipping features, which V8 considers stable, are turned on by default on Node.js and do NOT require any kind of runtime flag.
- Staged features, which are almost-completed features that are not considered stable by the V8 team, require a runtime flag:
--harmony
. - In progress features can be activated individually by their respective harmony flag, although this is highly discouraged unless for testing purposes. Note: these flags are exposed by V8 and will potentially change without any deprecation notice.
Guides
General
- Getting Started Guide
- Debugging - Getting Started
- Easy profiling for Node.js Applications
- Diagnostics - Flame Graphs
- Dockerizing a Node.js web app
- Migrating to safe Buffer constructors
Node.js core concepts
- Introduction to Node.js
- Overview of Blocking vs Non-Blocking
- The Node.js Event Loop, Timers, and
process.nextTick()
- Don't Block the Event Loop (or the Worker Pool)
- Timers in Node.js