@types/node 20.12.7 → 20.12.9

node/timers.d.ts

@@ -6,7 +6,7 @@
  * The timer functions within Node.js implement a similar API as the timers API
  * provided by Web Browsers but use a different internal implementation that is
  * built around the Node.js [Event Loop](https://nodejs.org/en/docs/guides/event-loop-timers-and-nexttick/#setimmediate-vs-settimeout).
- * @see [source](https://github.com/nodejs/node/blob/v20.2.0/lib/timers.js)
+ * @see [source](https://github.com/nodejs/node/blob/v20.12.2/lib/timers.js)
  */
 declare module "timers" {
     import { Abortable } from "node:events";
@@ -43,12 +43,12 @@ declare module "timers" {
              * actions.
              *
              * By default, when an immediate is scheduled, the Node.js event loop will continue
-             * running as long as the immediate is active. The `Immediate` object returned by `setImmediate()` exports both `immediate.ref()` and `immediate.unref()`functions that can be used to
+             * running as long as the immediate is active. The `Immediate` object returned by `setImmediate()` exports both `immediate.ref()` and `immediate.unref()` functions that can be used to
              * control this default behavior.
              */
             class Immediate implements RefCounted {
                 /**
-                 * When called, requests that the Node.js event loop _not_ exit so long as the`Immediate` is active. Calling `immediate.ref()` multiple times will have no
+                 * When called, requests that the Node.js event loop _not_ exit so long as the `Immediate` is active. Calling `immediate.ref()` multiple times will have no
                  * effect.
                  *
                  * By default, all `Immediate` objects are "ref'ed", making it normally unnecessary
@@ -100,7 +100,7 @@ declare module "timers" {
                 /**
                  * When called, the active `Timeout` object will not require the Node.js event loop
                  * to remain active. If there is no other activity keeping the event loop running,
-                 * the process may exit before the `Timeout` object's callback is invoked. Calling`timeout.unref()` multiple times will have no effect.
+                 * the process may exit before the `Timeout` object's callback is invoked. Calling `timeout.unref()` multiple times will have no effect.
                  * @since v0.9.1
                  * @return a reference to `timeout`
                  */
@@ -138,7 +138,7 @@ declare module "timers" {
          * nor of their ordering. The callback will be called as close as possible to the
          * time specified.
          *
-         * When `delay` is larger than `2147483647` or less than `1`, the `delay`will be set to `1`. Non-integer delays are truncated to an integer.
+         * When `delay` is larger than `2147483647` or less than `1`, the `delay` will be set to `1`. Non-integer delays are truncated to an integer.
          *
          * If `callback` is not a function, a `TypeError` will be thrown.
          *

node/tls.d.ts

@@ -6,7 +6,7 @@
  * ```js
  * const tls = require('node:tls');
  * ```
- * @see [source](https://github.com/nodejs/node/blob/v20.2.0/lib/tls.js)
+ * @see [source](https://github.com/nodejs/node/blob/v20.12.2/lib/tls.js)
  */
 declare module "tls" {
     import { X509Certificate } from "node:crypto";
@@ -125,7 +125,7 @@ declare module "tls" {
          */
         asn1Curve?: string;
         /**
-         * The NIST name for the elliptic curve,if it has one
+         * The NIST name for the elliptic curve, if it has one
          * (not all well-known curves have been assigned names by NIST).
          */
         nistCurve?: string;
@@ -278,7 +278,7 @@ declare module "tls" {
          * an ephemeral key exchange in `perfect forward secrecy` on a client
          * connection. It returns an empty object when the key exchange is not
          * ephemeral. As this is only supported on a client socket; `null` is returned
-         * if called on a server socket. The supported types are `'DH'` and `'ECDH'`. The`name` property is available only when type is `'ECDH'`.
+         * if called on a server socket. The supported types are `'DH'` and `'ECDH'`. The `name` property is available only when type is `'ECDH'`.
          *
          * For example: `{ type: 'ECDH', name: 'prime256v1', size: 256 }`.
          * @since v5.0.0
@@ -382,7 +382,7 @@ declare module "tls" {
          * This method can be used to request a peer's certificate after the secure
          * connection has been established.
          *
-         * When running as the server, the socket will be destroyed with an error after`handshakeTimeout` timeout.
+         * When running as the server, the socket will be destroyed with an error after `handshakeTimeout` timeout.
          *
          * For TLSv1.3, renegotiation cannot be initiated, it is not supported by the
          * protocol.
@@ -975,7 +975,7 @@ declare module "tls" {
      * This function is intended to be used in combination with the`checkServerIdentity` option that can be passed to {@link connect} and as
      * such operates on a `certificate object`. For other purposes, consider using `x509.checkHost()` instead.
      *
-     * This function can be overwritten by providing an alternative function as the`options.checkServerIdentity` option that is passed to `tls.connect()`. The
+     * This function can be overwritten by providing an alternative function as the `options.checkServerIdentity` option that is passed to `tls.connect()`. The
      * overwriting function can call `tls.checkServerIdentity()` of course, to augment
      * the checks done with additional verification.
      *
@@ -984,7 +984,7 @@ declare module "tls" {
      *
      * Earlier versions of Node.js incorrectly accepted certificates for a given`hostname` if a matching `uniformResourceIdentifier` subject alternative name
      * was present (see [CVE-2021-44531](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44531)). Applications that wish to accept`uniformResourceIdentifier` subject alternative names can use
-     * a custom`options.checkServerIdentity` function that implements the desired behavior.
+     * a custom `options.checkServerIdentity` function that implements the desired behavior.
      * @since v0.8.4
      * @param hostname The host name or IP address to verify the certificate against.
      * @param cert A `certificate object` representing the peer's certificate.
@@ -1092,7 +1092,7 @@ declare module "tls" {
      * stream and the cleartext one is used as a replacement for the initial encrypted
      * stream.
      *
-     * `tls.createSecurePair()` returns a `tls.SecurePair` object with `cleartext` and`encrypted` stream properties.
+     * `tls.createSecurePair()` returns a `tls.SecurePair` object with `cleartext` and `encrypted` stream properties.
      *
      * Using `cleartext` has the same API as {@link TLSSocket}.
      *
@@ -1125,10 +1125,10 @@ declare module "tls" {
         rejectUnauthorized?: boolean,
     ): SecurePair;
     /**
-     * {@link createServer} sets the default value of the `honorCipherOrder` option
+     * `{@link createServer}` sets the default value of the `honorCipherOrder` option
      * to `true`, other APIs that create secure contexts leave it unset.
      *
-     * {@link createServer} uses a 128 bit truncated SHA1 hash value generated
+     * `{@link createServer}` uses a 128 bit truncated SHA1 hash value generated
      * from `process.argv` as the default value of the `sessionIdContext` option, other
      * APIs that create secure contexts have no default value.
      *
@@ -1136,12 +1136,12 @@ declare module "tls" {
      * usable as an argument to several `tls` APIs, such as `server.addContext()`,
      * but has no public methods. The {@link Server} constructor and the {@link createServer} method do not support the `secureContext` option.
      *
-     * A key is _required_ for ciphers that use certificates. Either `key` or`pfx` can be used to provide it.
+     * A key is _required_ for ciphers that use certificates. Either `key` or `pfx` can be used to provide it.
      *
      * If the `ca` option is not given, then Node.js will default to using [Mozilla's publicly trusted list of
      * CAs](https://hg.mozilla.org/mozilla-central/raw-file/tip/security/nss/lib/ckfw/builtins/certdata.txt).
      *
-     * Custom DHE parameters are discouraged in favor of the new `dhparam: 'auto'`option. When set to `'auto'`, well-known DHE parameters of sufficient strength
+     * Custom DHE parameters are discouraged in favor of the new `dhparam: 'auto' `option. When set to `'auto'`, well-known DHE parameters of sufficient strength
      * will be selected automatically. Otherwise, if necessary, `openssl dhparam` can
      * be used to create custom parameters. The key length must be greater than or
      * equal to 1024 bits or else an error will be thrown. Although 1024 bits is
@@ -1152,9 +1152,10 @@ declare module "tls" {
     /**
      * Returns an array with the names of the supported TLS ciphers. The names are
      * lower-case for historical reasons, but must be uppercased to be used in
-     * the `ciphers` option of {@link createSecureContext}.
+     * the `ciphers` option of `{@link createSecureContext}`.
      *
-     * Not all supported ciphers are enabled by default. See `Modifying the default TLS cipher suite`.
+     * Not all supported ciphers are enabled by default. See
+     * [Modifying the default TLS cipher suite](https://nodejs.org/docs/latest-v20.x/api/tls.html#modifying-the-default-tls-cipher-suite).
      *
      * Cipher names that start with `'tls_'` are for TLSv1.3, all the others are for
      * TLSv1.2 and below.
@@ -1167,41 +1168,47 @@ declare module "tls" {
     function getCiphers(): string[];
     /**
      * The default curve name to use for ECDH key agreement in a tls server.
-     * The default value is 'auto'. See tls.createSecureContext() for further
+     * The default value is `'auto'`. See `{@link createSecureContext()}` for further
      * information.
+     * @since v0.11.13
      */
     let DEFAULT_ECDH_CURVE: string;
     /**
-     * The default value of the maxVersion option of
-     * tls.createSecureContext(). It can be assigned any of the supported TLS
-     * protocol versions, 'TLSv1.3', 'TLSv1.2', 'TLSv1.1', or 'TLSv1'. Default:
-     * 'TLSv1.3', unless changed using CLI options. Using --tls-max-v1.2 sets
-     * the default to 'TLSv1.2'. Using --tls-max-v1.3 sets the default to
-     * 'TLSv1.3'. If multiple of the options are provided, the highest maximum
-     * is used.
+     * The default value of the `maxVersion` option of `{@link createSecureContext()}`.
+     * It can be assigned any of the supported TLS protocol versions,
+     * `'TLSv1.3'`, `'TLSv1.2'`, `'TLSv1.1'`, or `'TLSv1'`. **Default:** `'TLSv1.3'`, unless
+     * changed using CLI options. Using `--tls-max-v1.2` sets the default to `'TLSv1.2'`. Using
+     * `--tls-max-v1.3` sets the default to `'TLSv1.3'`. If multiple of the options
+     * are provided, the highest maximum is used.
+     * @since v11.4.0
      */
     let DEFAULT_MAX_VERSION: SecureVersion;
     /**
-     * The default value of the minVersion option of tls.createSecureContext().
+     * The default value of the `minVersion` option of `{@link createSecureContext()}`.
      * It can be assigned any of the supported TLS protocol versions,
-     * 'TLSv1.3', 'TLSv1.2', 'TLSv1.1', or 'TLSv1'. Default: 'TLSv1.2', unless
-     * changed using CLI options. Using --tls-min-v1.0 sets the default to
-     * 'TLSv1'. Using --tls-min-v1.1 sets the default to 'TLSv1.1'. Using
-     * --tls-min-v1.3 sets the default to 'TLSv1.3'. If multiple of the options
+     * `'TLSv1.3'`, `'TLSv1.2'`, `'TLSv1.1'`, or `'TLSv1'`. **Default:** `'TLSv1.2'`, unless
+     * changed using CLI options. Using `--tls-min-v1.0` sets the default to
+     * `'TLSv1'`. Using `--tls-min-v1.1` sets the default to `'TLSv1.1'`. Using
+     * `--tls-min-v1.3` sets the default to `'TLSv1.3'`. If multiple of the options
      * are provided, the lowest minimum is used.
+     * @since v11.4.0
      */
     let DEFAULT_MIN_VERSION: SecureVersion;
     /**
-     * The default value of the ciphers option of tls.createSecureContext().
+     * The default value of the `ciphers` option of `{@link createSecureContext()}`.
      * It can be assigned any of the supported OpenSSL ciphers.
-     * Defaults to the content of crypto.constants.defaultCoreCipherList, unless
-     * changed using CLI options using --tls-default-ciphers.
+     * Defaults to the content of `crypto.constants.defaultCoreCipherList`, unless
+     * changed using CLI options using `--tls-default-ciphers`.
+     * @since v19.8.0
      */
     let DEFAULT_CIPHERS: string;
     /**
-     * An immutable array of strings representing the root certificates (in PEM
-     * format) used for verifying peer certificates. This is the default value
-     * of the ca option to tls.createSecureContext().
+     * An immutable array of strings representing the root certificates (in PEM format)
+     * from the bundled Mozilla CA store as supplied by the current Node.js version.
+     *
+     * The bundled CA store, as supplied by Node.js, is a snapshot of Mozilla CA store
+     * that is fixed at release time. It is identical on all supported platforms.
+     * @since v12.3.0
      */
     const rootCertificates: readonly string[];
 }

node/trace_events.d.ts

@@ -1,40 +1,36 @@
 /**
- * The `node:trace_events` module provides a mechanism to centralize tracing
- * information generated by V8, Node.js core, and userspace code.
+ * The `node:trace_events` module provides a mechanism to centralize tracing information
+ * generated by V8, Node.js core, and userspace code.
  *
  * Tracing can be enabled with the `--trace-event-categories` command-line flag
- * or by using the `node:trace_events` module. The `--trace-event-categories` flag
+ * or by using the `trace_events` module. The `--trace-event-categories` flag
  * accepts a list of comma-separated category names.
  *
  * The available categories are:
  *
  * * `node`: An empty placeholder.
- * * `node.async_hooks`: Enables capture of detailed `async_hooks` trace data.
- * The `async_hooks` events have a unique `asyncId` and a special `triggerId` `triggerAsyncId` property.
+ * * `node.async_hooks`: Enables capture of detailed [`async_hooks`](https://nodejs.org/docs/latest-v20.x/api/async_hooks.html) trace data.
+ * The [`async_hooks`](https://nodejs.org/docs/latest-v20.x/api/async_hooks.html) events have a unique `asyncId` and a special `triggerId` `triggerAsyncId` property.
  * * `node.bootstrap`: Enables capture of Node.js bootstrap milestones.
- * * `node.console`: Enables capture of `console.time()` and `console.count()`output.
- * * `node.threadpoolwork.sync`: Enables capture of trace data for threadpool
- * synchronous operations, such as `blob`, `zlib`, `crypto` and `node_api`.
- * * `node.threadpoolwork.async`: Enables capture of trace data for threadpool
- * asynchronous operations, such as `blob`, `zlib`, `crypto` and `node_api`.
+ * * `node.console`: Enables capture of `console.time()` and `console.count()` output.
+ * * `node.threadpoolwork.sync`: Enables capture of trace data for threadpool synchronous operations, such as `blob`, `zlib`, `crypto` and `node_api`.
+ * * `node.threadpoolwork.async`: Enables capture of trace data for threadpool asynchronous operations, such as `blob`, `zlib`, `crypto` and `node_api`.
  * * `node.dns.native`: Enables capture of trace data for DNS queries.
  * * `node.net.native`: Enables capture of trace data for network.
  * * `node.environment`: Enables capture of Node.js Environment milestones.
  * * `node.fs.sync`: Enables capture of trace data for file system sync methods.
- * * `node.fs_dir.sync`: Enables capture of trace data for file system sync
- * directory methods.
+ * * `node.fs_dir.sync`: Enables capture of trace data for file system sync directory methods.
  * * `node.fs.async`: Enables capture of trace data for file system async methods.
- * * `node.fs_dir.async`: Enables capture of trace data for file system async
- * directory methods.
- * * `node.perf`: Enables capture of `Performance API` measurements.
+ * * `node.fs_dir.async`: Enables capture of trace data for file system async directory methods.
+ * * `node.perf`: Enables capture of [Performance API](https://nodejs.org/docs/latest-v20.x/api/perf_hooks.html) measurements.
  *    * `node.perf.usertiming`: Enables capture of only Performance API User Timing
  *    measures and marks.
  *    * `node.perf.timerify`: Enables capture of only Performance API timerify
  *    measurements.
  * * `node.promises.rejections`: Enables capture of trace data tracking the number
  * of unhandled Promise rejections and handled-after-rejections.
- * * `node.vm.script`: Enables capture of trace data for the `node:vm` module's`runInNewContext()`, `runInContext()`, and `runInThisContext()` methods.
- * * `v8`: The `V8` events are GC, compiling, and execution related.
+ * * `node.vm.script`: Enables capture of trace data for the `node:vm` module's `runInNewContext()`, `runInContext()`, and `runInThisContext()` methods.
+ * * `v8`: The [V8](https://nodejs.org/docs/latest-v20.x/api/v8.html) events are GC, compiling, and execution related.
  * * `node.http`: Enables capture of trace data for http request / response.
  *
  * By default the `node`, `node.async_hooks`, and `v8` categories are enabled.
@@ -43,8 +39,8 @@
  * node --trace-event-categories v8,node,node.async_hooks server.js
  * ```
  *
- * Prior versions of Node.js required the use of the `--trace-events-enabled`flag to enable trace events. This requirement has been removed. However, the`--trace-events-enabled` flag _may_ still be
- * used and will enable the`node`, `node.async_hooks`, and `v8` trace event categories by default.
+ * Prior versions of Node.js required the use of the `--trace-events-enabled` flag to enable trace events. This requirement has been removed. However, the `--trace-events-enabled` flag _may_ still be
+ * used and will enable the `node`, `node.async_hooks`, and `v8` trace event categories by default.
  *
  * ```bash
  * node --trace-events-enabled
@@ -69,7 +65,7 @@
  * Running Node.js with tracing enabled will produce log files that can be opened
  * in the [`chrome://tracing`](https://www.chromium.org/developers/how-tos/trace-event-profiling-tool) tab of Chrome.
  *
- * The logging file is by default called `node_trace.${rotation}.log`, where`${rotation}` is an incrementing log-rotation id. The filepath pattern can
+ * The logging file is by default called `node_trace.${rotation}.log`, where `${rotation}` is an incrementing log-rotation id. The filepath pattern can
  * be specified with `--trace-event-file-pattern` that accepts a template
  * string that supports `${rotation}` and `${pid}`:
  *
@@ -77,7 +73,7 @@
  * node --trace-event-categories v8 --trace-event-file-pattern '${pid}-${rotation}.log' server.js
  * ```
  *
- * To guarantee that the log file is properly generated after signal events like`SIGINT`, `SIGTERM`, or `SIGBREAK`, make sure to have the appropriate handlers
+ * To guarantee that the log file is properly generated after signal events like `SIGINT`, `SIGTERM`, or `SIGBREAK`, make sure to have the appropriate handlers
  * in your code, such as:
  *
  * ```js
@@ -92,9 +88,9 @@
  * However the trace-event timestamps are expressed in microseconds,
  * unlike `process.hrtime()` which returns nanoseconds.
  *
- * The features from this module are not available in `Worker` threads.
+ * The features from this module are not available in [`Worker`](https://nodejs.org/docs/latest-v20.x/api/worker_threads.html#class-worker) threads.
  * @experimental
- * @see [source](https://github.com/nodejs/node/blob/v20.2.0/lib/trace_events.js)
+ * @see [source](https://github.com/nodejs/node/blob/v20.12.2/lib/trace_events.js)
  */
 declare module "trace_events" {
     /**
@@ -111,6 +107,7 @@ declare module "trace_events" {
         /**
          * A comma-separated list of the trace event categories covered by this
          * `Tracing` object.
+         * @since v10.0.0
          */
         readonly categories: string;
         /**
@@ -119,15 +116,34 @@ declare module "trace_events" {
          * Only trace event categories _not_ covered by other enabled `Tracing`
          * objects and _not_ specified by the `--trace-event-categories` flag
          * will be disabled.
+         *
+         * ```js
+         * const trace_events = require('node:trace_events');
+         * const t1 = trace_events.createTracing({ categories: ['node', 'v8'] });
+         * const t2 = trace_events.createTracing({ categories: ['node.perf', 'node'] });
+         * t1.enable();
+         * t2.enable();
+         *
+         * // Prints 'node,node.perf,v8'
+         * console.log(trace_events.getEnabledCategories());
+         *
+         * t2.disable(); // Will only disable emission of the 'node.perf' category
+         *
+         * // Prints 'node,v8'
+         * console.log(trace_events.getEnabledCategories());
+         * ```
+         * @since v10.0.0
          */
         disable(): void;
         /**
          * Enables this `Tracing` object for the set of categories covered by
          * the `Tracing` object.
+         * @since v10.0.0
          */
         enable(): void;
         /**
          * `true` only if the `Tracing` object has been enabled.
+         * @since v10.0.0
          */
         readonly enabled: boolean;
     }
@@ -151,7 +167,6 @@ declare module "trace_events" {
      * tracing.disable();
      * ```
      * @since v10.0.0
-     * @return .
      */
     function createTracing(options: CreateTracingOptions): Tracing;
     /**
@@ -160,7 +175,7 @@ declare module "trace_events" {
      * by the _union_ of all currently-enabled `Tracing` objects and any categories
      * enabled using the `--trace-event-categories` flag.
      *
-     * Given the file `test.js` below, the command`node --trace-event-categories node.perf test.js` will print`'node.async_hooks,node.perf'` to the console.
+     * Given the file `test.js` below, the command `node --trace-event-categories node.perf test.js` will print `'node.async_hooks,node.perf'` to the console.
      *
      * ```js
      * const trace_events = require('node:trace_events');

node/tty.d.ts

@@ -1,5 +1,5 @@
 /**
- * The `node:tty` module provides the `tty.ReadStream` and `tty.WriteStream`classes. In most cases, it will not be necessary or possible to use this module
+ * The `node:tty` module provides the `tty.ReadStream` and `tty.WriteStream` classes. In most cases, it will not be necessary or possible to use this module
  * directly. However, it can be accessed using:
  *
  * ```js
@@ -7,7 +7,7 @@
  * ```
  *
  * When Node.js detects that it is being run with a text terminal ("TTY")
- * attached, `process.stdin` will, by default, be initialized as an instance of`tty.ReadStream` and both `process.stdout` and `process.stderr` will, by
+ * attached, `process.stdin` will, by default, be initialized as an instance of `tty.ReadStream` and both `process.stdout` and `process.stderr` will, by
  * default, be instances of `tty.WriteStream`. The preferred method of determining
  * whether Node.js is being run within a TTY context is to check that the value of
  * the `process.stdout.isTTY` property is `true`:
@@ -20,8 +20,8 @@
  * ```
  *
  * In most cases, there should be little to no reason for an application to
- * manually create instances of the `tty.ReadStream` and `tty.WriteStream`classes.
- * @see [source](https://github.com/nodejs/node/blob/v20.2.0/lib/tty.js)
+ * manually create instances of the `tty.ReadStream` and `tty.WriteStream` classes.
+ * @see [source](https://github.com/nodejs/node/blob/v20.12.2/lib/tty.js)
  */
 declare module "tty" {
     import * as net from "node:net";
@@ -45,7 +45,7 @@ declare module "tty" {
          * raw device.
          *
          * This flag is always `false` when a process starts, even if the terminal is
-         * operating in raw mode. Its value will change with subsequent calls to`setRawMode`.
+         * operating in raw mode. Its value will change with subsequent calls to `setRawMode`.
          * @since v0.7.7
          */
         isRaw: boolean;
@@ -76,7 +76,7 @@ declare module "tty" {
      */
     type Direction = -1 | 0 | 1;
     /**
-     * Represents the writable side of a TTY. In normal circumstances,`process.stdout` and `process.stderr` will be the only`tty.WriteStream` instances created for a Node.js process and there
+     * Represents the writable side of a TTY. In normal circumstances, `process.stdout` and `process.stderr` will be the only`tty.WriteStream` instances created for a Node.js process and there
      * should be no reason to create additional instances.
      * @since v0.5.8
      */
@@ -149,7 +149,7 @@ declare module "tty" {
          * * 256 colors: `FORCE_COLOR = 2`
          * * 16,777,216 colors: `FORCE_COLOR = 3`
          *
-         * Disabling color support is also possible by using the `NO_COLOR` and`NODE_DISABLE_COLORS` environment variables.
+         * Disabling color support is also possible by using the `NO_COLOR` and `NODE_DISABLE_COLORS` environment variables.
          * @since v9.9.0
          * @param [env=process.env] An object containing the environment variables to check. This enables simulating the usage of a specific terminal.
          */
@@ -179,7 +179,7 @@ declare module "tty" {
         hasColors(count: number, env?: object): boolean;
         /**
          * `writeStream.getWindowSize()` returns the size of the TTY
-         * corresponding to this `WriteStream`. The array is of the type`[numColumns, numRows]` where `numColumns` and `numRows` represent the number
+         * corresponding to this `WriteStream`. The array is of the type `[numColumns, numRows]` where `numColumns` and `numRows` represent the number
          * of columns and rows in the corresponding TTY.
          * @since v0.7.7
          */

node/url.d.ts

@@ -5,7 +5,7 @@
  * ```js
  * import url from 'node:url';
  * ```
- * @see [source](https://github.com/nodejs/node/blob/v20.11.0/lib/url.js)
+ * @see [source](https://github.com/nodejs/node/blob/v20.12.2/lib/url.js)
  */
 declare module "url" {
     import { Blob as NodeBlob } from "node:buffer";
@@ -503,9 +503,9 @@ declare module "url" {
          * Getting the value of the `href` property is equivalent to calling {@link toString}.
          *
          * Setting the value of this property to a new value is equivalent to creating a
-         * new `URL` object using `new URL(value)`. Each of the `URL`object's properties will be modified.
+         * new `URL` object using `new URL(value)`. Each of the `URL` object's properties will be modified.
          *
-         * If the value assigned to the `href` property is not a valid URL, a `TypeError`will be thrown.
+         * If the value assigned to the `href` property is not a valid URL, a `TypeError` will be thrown.
          */
         href: string;
         /**
@@ -664,7 +664,7 @@ declare module "url" {
          * // Prints https://example.org/abc?abc=xyz
          * ```
          *
-         * Any invalid URL characters appearing in the value assigned the `search`property will be `percent-encoded`. The selection of which
+         * Any invalid URL characters appearing in the value assigned the `search` property will be `percent-encoded`. The selection of which
          * characters to percent-encode may vary somewhat from what the {@link parse} and {@link format} methods would produce.
          */
         search: string;
@@ -858,7 +858,7 @@ declare module "url" {
          */
         keys(): IterableIterator<string>;
         /**
-         * Sets the value in the `URLSearchParams` object associated with `name` to`value`. If there are any pre-existing name-value pairs whose names are `name`,
+         * Sets the value in the `URLSearchParams` object associated with `name` to `value`. If there are any pre-existing name-value pairs whose names are `name`,
          * set the first such pair's value to `value` and remove all others. If not,
          * append the name-value pair to the query string.
          *