diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 56632fda4c67eb..f99a8abb394d14 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,9 +1,9 @@
-The `DiffieHellmanGroup` class takes a well-known modp group as its argument but
-otherwise works the same as `DiffieHellman`.
+The `DiffieHellmanGroup` class takes a well-known modp group as its argument.
+It works the same as `DiffieHellman`, except that it does not allow changing
+its keys after creation. In other words, it does not implement `setPublicKey()`
+or `setPrivateKey()` methods.
```mjs
const { createDiffieHellmanGroup } = await import('crypto');
@@ -1399,7 +1401,7 @@ Example (obtaining a shared secret):
const {
createECDH,
createHash,
-} = await crypto('crypto');
+} = await import('crypto');
const alice = createECDH('secp256k1');
const bob = createECDH('secp256k1');
diff --git a/doc/api/debugger.md b/doc/api/debugger.md
index f17750ac116302..66a97f36ec5ee9 100644
--- a/doc/api/debugger.md
+++ b/doc/api/debugger.md
@@ -67,7 +67,7 @@ break in myscript.js:4
5 }, 1000);
6 console.log('hello');
debug> repl
-Press Ctrl + C to leave debug repl
+Press Ctrl+C to leave debug repl
> x
5
> 2 + 2
diff --git a/doc/api/deprecations.md b/doc/api/deprecations.md
index cc6b61206c5efe..a0140b16e9b7cc 100644
--- a/doc/api/deprecations.md
+++ b/doc/api/deprecations.md
@@ -831,12 +831,15 @@ The [`require.extensions`][] property is deprecated.
### DEP0040: `punycode` module
-Type: Documentation-only
+Type: Documentation-only (supports [`--pending-deprecation`][])
The [`punycode`][] module is deprecated. Please use a userland alternative
instead.
diff --git a/doc/api/errors.md b/doc/api/errors.md
index e8b416949da7c8..3ff3c5c1797332 100644
--- a/doc/api/errors.md
+++ b/doc/api/errors.md
@@ -714,6 +714,22 @@ Used when a child process is being forked without specifying an IPC channel.
Used when the main process is trying to read data from the child process's
STDERR/STDOUT, and the data's length is longer than the `maxBuffer` option.
+
+### `ERR_CLOSED_MESSAGE_PORT`
+
+
+There was an attempt to use a `MessagePort` instance in a closed
+state, usually after `.close()` has been called.
+
### `ERR_CONSOLE_WRITABLE_STREAM`
@@ -2460,16 +2476,6 @@ removed: v12.5.0
The value passed to `postMessage()` contained an object that is not supported
for transferring.
-
-### `ERR_CLOSED_MESSAGE_PORT`
-
-
-There was an attempt to use a `MessagePort` instance in a closed
-state, usually after `.close()` has been called.
-
### `ERR_CRYPTO_HASH_DIGEST_NO_UTF16`
+* `stream` {Http2Stream} A reference to the stream
+* `headers` {HTTP/2 Headers Object} An object describing the headers
+* `flags` {number} The associated numeric flags
+* `rawHeaders` {Array} An array containing the raw header names followed by
+ their respective values.
+
The `'stream'` event is emitted when a `'stream'` event has been emitted by
an `Http2Session` associated with the server.
+See also [`Http2Session`'s `'stream'` event][].
+
```js
const http2 = require('http2');
const {
@@ -2003,9 +2018,17 @@ an `Http2Session` object associated with the `Http2SecureServer`.
added: v8.4.0
-->
+* `stream` {Http2Stream} A reference to the stream
+* `headers` {HTTP/2 Headers Object} An object describing the headers
+* `flags` {number} The associated numeric flags
+* `rawHeaders` {Array} An array containing the raw header names followed by
+ their respective values.
+
The `'stream'` event is emitted when a `'stream'` event has been emitted by
an `Http2Session` associated with the server.
+See also [`Http2Session`'s `'stream'` event][].
+
```js
const http2 = require('http2');
const {
@@ -3838,6 +3861,7 @@ you need to implement any fall-back behaviour yourself.
[`Http2ServerRequest`]: #http2_class_http2_http2serverrequest
[`Http2ServerResponse`]: #http2_class_http2_http2serverresponse
[`Http2Session` and Sockets]: #http2_http2session_and_sockets
+[`Http2Session`'s `'stream'` event]: #http2_event_stream
[`Http2Stream`]: #http2_class_http2stream
[`ServerHttp2Stream`]: #http2_class_serverhttp2stream
[`TypeError`]: errors.md#errors_class_typeerror
diff --git a/doc/api/n-api.md b/doc/api/n-api.md
index 01e365ac050183..3e31c638cece40 100644
--- a/doc/api/n-api.md
+++ b/doc/api/n-api.md
@@ -286,12 +286,14 @@ listed as supporting a later version.
5
6
7
+
8
v10.x
v10.16.0
v10.17.0
v10.20.0
+
v10.23.0
@@ -300,6 +302,7 @@ listed as supporting a later version.
+
v12.x
@@ -307,6 +310,7 @@ listed as supporting a later version.
v12.11.0
v12.17.0
v12.19.0
+
v12.22.0
v13.x
@@ -314,6 +318,7 @@ listed as supporting a later version.
v13.0.0
+
v14.x
@@ -321,6 +326,23 @@ listed as supporting a later version.
v14.0.0
v14.0.0
v14.12.0
+
+
+
+
v15.x
+
v15.0.0
+
v15.0.0
+
v15.0.0
+
v15.0.0
+
v15.12.0
+
+
+
v16.x
+
v16.0.0
+
v16.0.0
+
v16.0.0
+
v16.0.0
+
v16.0.0
diff --git a/doc/api/net.md b/doc/api/net.md
index 699b1ba4d573b8..5066179046c8c1 100644
--- a/doc/api/net.md
+++ b/doc/api/net.md
@@ -551,9 +551,10 @@ changes:
* `options` {Object} Available options are:
* `fd` {number} If specified, wrap around an existing socket with
the given file descriptor, otherwise a new socket will be created.
- * `allowHalfOpen` {boolean} Indicates whether half-opened TCP connections
- are allowed. See [`net.createServer()`][] and the [`'end'`][] event
- for details. **Default:** `false`.
+ * `allowHalfOpen` {boolean} If set to `false`, then the socket will
+ automatically end the writable side when the readable side ends. See
+ [`net.createServer()`][] and the [`'end'`][] event for details. **Default:**
+ `false`.
* `readable` {boolean} Allow reads on the socket when an `fd` is passed,
otherwise ignored. **Default:** `false`.
* `writable` {boolean} Allow writes on the socket when an `fd` is passed,
@@ -612,14 +613,14 @@ See also: the return values of `socket.write()`.
added: v0.1.90
-->
-Emitted when the other end of the socket sends a FIN packet, thus ending the
-readable side of the socket.
+Emitted when the other end of the socket signals the end of transmission, thus
+ending the readable side of the socket.
-By default (`allowHalfOpen` is `false`) the socket will send a FIN packet
-back and destroy its file descriptor once it has written out its pending
-write queue. However, if `allowHalfOpen` is set to `true`, the socket will
-not automatically [`end()`][`socket.end()`] its writable side, allowing the
-user to write arbitrary amounts of data. The user must call
+By default (`allowHalfOpen` is `false`) the socket will send an end of
+transmission packet back and destroy its file descriptor once it has written out
+its pending write queue. However, if `allowHalfOpen` is set to `true`, the
+socket will not automatically [`end()`][`socket.end()`] its writable side,
+allowing the user to write arbitrary amounts of data. The user must call
[`end()`][`socket.end()`] explicitly to close the connection (i.e. sending a
FIN packet back).
@@ -1006,6 +1007,12 @@ Set the encoding for the socket as a [Readable Stream][]. See
### `socket.setKeepAlive([enable][, initialDelay])`
* `enable` {boolean} **Default:** `false`
@@ -1020,6 +1027,12 @@ data packet received and the first keepalive probe. Setting `0` for
`initialDelay` will leave the value unchanged from the default
(or previous) setting.
+Enabling the keep-alive functionality will set the following socket options:
+* `SO_KEEPALIVE=1`
+* `TCP_KEEPIDLE=initialDelay`
+* `TCP_KEEPCNT=10`
+* `TCP_KEEPINTVL=1`
+
### `socket.setNoDelay([noDelay])`
* `options` {Object}
- * `allowHalfOpen` {boolean} Indicates whether half-opened TCP
- connections are allowed. **Default:** `false`.
+ * `allowHalfOpen` {boolean} If set to `false`, then the socket will
+ automatically end the writable side when the readable side ends.
+ **Default:** `false`.
* `pauseOnConnect` {boolean} Indicates whether the socket should be
paused on incoming connections. **Default:** `false`.
* `connectionListener` {Function} Automatically set as a listener for the
@@ -1306,10 +1320,12 @@ added: v0.5.0
Creates a new TCP or [IPC][] server.
If `allowHalfOpen` is set to `true`, when the other end of the socket
-sends a FIN packet, the server will only send a FIN packet back when
-[`socket.end()`][] is explicitly called, until then the connection is
-half-closed (non-readable but still writable). See [`'end'`][] event
-and [RFC 1122][half-closed] (section 4.2.2.13) for more information.
+signals the end of transmission, the server will only send back the end of
+transmission when [`socket.end()`][] is explicitly called. For example, in the
+context of TCP, when a FIN packed is received, a FIN packed is sent
+back only when [`socket.end()`][] is explicitly called. Until then the
+connection is half-closed (non-readable but still writable). See [`'end'`][]
+event and [RFC 1122][half-closed] (section 4.2.2.13) for more information.
If `pauseOnConnect` is set to `true`, then the socket associated with each
incoming connection will be paused, and no data will be read from its handle.
diff --git a/doc/api/os.md b/doc/api/os.md
index 6e84a322207a57..f3d3f2d65249a4 100644
--- a/doc/api/os.md
+++ b/doc/api/os.md
@@ -368,18 +368,6 @@ changes:
Returns the system uptime in number of seconds.
-The value returned can be inaccurate in some
-rare virtualization cases. The issue arises when the virtualized
-guest instance shares the kernel with the host system.
-Due to the fact that libuv uses a syscall that
-provides host's uptime instead of guest's
-uptime on OpenVZ, `os.uptime()` may also provide
-erroneous result.
-
-Please refer to and
- for an exploration of
-this issue, until it is resolved by libuv.
-
## `os.userInfo([options])`
For packages with a small number of exports or imports, we recommend
@@ -428,7 +428,7 @@ The benefit of patterns over folder exports is that packages can always be
imported by consumers without subpath file extensions being necessary.
### Exports sugar
-
@@ -455,7 +455,7 @@ can be written:
```
### Conditional exports
-
* Type: {Object}
diff --git a/doc/api/path.md b/doc/api/path.md
index ca62e2f3628bfe..839c45da906677 100644
--- a/doc/api/path.md
+++ b/doc/api/path.md
@@ -203,7 +203,7 @@ A [`TypeError`][] is thrown if `path` is not a string.
added: v0.11.15
-->
-* `pathObject` {Object}
+* `pathObject` {Object} Any JavaScript object having the following properties:
* `dir` {string}
* `root` {string}
* `base` {string}
diff --git a/doc/api/perf_hooks.md b/doc/api/perf_hooks.md
index 11795b98dc71fa..80a3c46f36a281 100644
--- a/doc/api/perf_hooks.md
+++ b/doc/api/perf_hooks.md
@@ -261,6 +261,14 @@ If the wrapped function returns a promise, a finally handler will be attached
to the promise and the duration will be reported once the finally handler is
invoked.
+### `performance.toJSON()`
+
+
+An object which is JSON representation of the `performance` object. It
+is similar to [`window.performance.toJSON`][] in browsers.
+
## Class: `PerformanceEntry`
+> Stability: 3 - Legacy. Use [`process.hrtime.bigint()`][] instead.
+
* `time` {integer[]} The result of a previous call to `process.hrtime()`
* Returns: {integer[]}
diff --git a/doc/api/querystring.md b/doc/api/querystring.md
index 2b8755df413914..4b7db7afc3b948 100644
--- a/doc/api/querystring.md
+++ b/doc/api/querystring.md
@@ -2,7 +2,7 @@
-> Stability: 2 - Stable
+> Stability: 3 - Legacy
@@ -15,6 +15,9 @@ query strings. It can be accessed using:
const querystring = require('querystring');
```
+The `querystring` API is considered Legacy. While it is still maintained,
+new code should use the {URLSearchParams} API instead.
+
## `querystring.decode()`
-* `keys` {Buffer} A 48-byte buffer containing the session ticket keys.
+* `keys` {Buffer|TypedArray|DataView} A 48-byte buffer containing the session
+ ticket keys.
Sets the session ticket keys.
@@ -849,6 +850,9 @@ determine if the server certificate was signed by one of the specified CAs. If
`tlsSocket.alpnProtocol` property can be checked to determine the negotiated
protocol.
+The `'secureConnect'` event is not emitted when a {tls.TLSSocket} is created
+using the `new tls.TLSSocket()` constructor.
+
### Event: `'session'`
@@ -666,7 +666,7 @@ Depending on how a `Buffer` instance was created, it may or may
not own its underlying `ArrayBuffer`. An `ArrayBuffer` must not
be transferred unless it is known that the `Buffer` instance
owns it. In particular, for `Buffer`s created from the internal
-`Buffer` pool (using, for instance `Buffer.from()` or `Buffer.alloc()`),
+`Buffer` pool (using, for instance `Buffer.from()` or `Buffer.allocUnsafe()`),
transferring them is not possible and they are always cloned,
which sends a copy of the entire `Buffer` pool.
This behavior may come with unintended higher memory
diff --git a/doc/changelogs/CHANGELOG_V16.md b/doc/changelogs/CHANGELOG_V16.md
index a198d504fe49ed..08ce83663289d5 100644
--- a/doc/changelogs/CHANGELOG_V16.md
+++ b/doc/changelogs/CHANGELOG_V16.md
@@ -10,6 +10,7 @@