node-red-contrib-tak-registration 0.14.1 → 0.16.0

package/node_modules/@types/node/timers.d.ts

@@ -10,12 +10,8 @@
  */
 declare module "timers" {
     import { Abortable } from "node:events";
-    import {
-        setImmediate as setImmediatePromise,
-        setInterval as setIntervalPromise,
-        setTimeout as setTimeoutPromise,
-    } from "node:timers/promises";
-    interface TimerOptions extends Abortable {
+    import * as promises from "node:timers/promises";
+    export interface TimerOptions extends Abortable {
         /**
          * Set to `false` to indicate that the scheduled `Timeout`
          * should not require the Node.js event loop to remain active.
@@ -23,38 +19,33 @@ declare module "timers" {
          */
         ref?: boolean | undefined;
     }
-    let setTimeout: typeof global.setTimeout;
-    let clearTimeout: typeof global.clearTimeout;
-    let setInterval: typeof global.setInterval;
-    let clearInterval: typeof global.clearInterval;
-    let setImmediate: typeof global.setImmediate;
-    let clearImmediate: typeof global.clearImmediate;
     global {
         namespace NodeJS {
-            // compatibility with older typings
-            interface Timer extends RefCounted {
-                hasRef(): boolean;
-                refresh(): this;
-                [Symbol.toPrimitive](): number;
-            }
             /**
              * This object is created internally and is returned from `setImmediate()`. It
              * can be passed to `clearImmediate()` in order to cancel the scheduled
              * 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
-             * control this default behavior.
+             * 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 {
+            interface Immediate extends RefCounted, Disposable {
+                /**
+                 * If true, the `Immediate` object will keep the Node.js event loop active.
+                 * @since v11.0.0
+                 */
+                hasRef(): boolean;
                 /**
-                 * 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
                  * to call `immediate.ref()` unless `immediate.unref()` had been called previously.
                  * @since v9.7.0
-                 * @return a reference to `immediate`
+                 * @returns a reference to `immediate`
                  */
                 ref(): this;
                 /**
@@ -63,53 +54,59 @@ declare module "timers" {
                  * running, the process may exit before the `Immediate` object's callback is
                  * invoked. Calling `immediate.unref()` multiple times will have no effect.
                  * @since v9.7.0
-                 * @return a reference to `immediate`
+                 * @returns a reference to `immediate`
                  */
                 unref(): this;
-                /**
-                 * If true, the `Immediate` object will keep the Node.js event loop active.
-                 * @since v11.0.0
-                 */
-                hasRef(): boolean;
-                _onImmediate: Function; // to distinguish it from the Timeout class
                 /**
                  * Cancels the immediate. This is similar to calling `clearImmediate()`.
-                 * @since v20.5.0
+                 * @since v20.5.0, v18.18.0
+                 * @experimental
                  */
                 [Symbol.dispose](): void;
+                _onImmediate(...args: any[]): void;
+            }
+            // Legacy interface used in Node.js v9 and prior
+            // TODO: remove in a future major version bump
+            /** @deprecated Use `NodeJS.Timeout` instead. */
+            interface Timer extends RefCounted {
+                hasRef(): boolean;
+                refresh(): this;
+                [Symbol.toPrimitive](): number;
             }
             /**
-             * This object is created internally and is returned from `setTimeout()` and `setInterval()`. It can be passed to either `clearTimeout()` or `clearInterval()` in order to cancel the
-             * scheduled actions.
+             * This object is created internally and is returned from `setTimeout()` and
+             * `setInterval()`. It can be passed to either `clearTimeout()` or
+             * `clearInterval()` in order to cancel the scheduled actions.
              *
-             * By default, when a timer is scheduled using either `setTimeout()` or `setInterval()`, the Node.js event loop will continue running as long as the
+             * By default, when a timer is scheduled using either `setTimeout()` or
+             * `setInterval()`, the Node.js event loop will continue running as long as the
              * timer is active. Each of the `Timeout` objects returned by these functions
              * export both `timeout.ref()` and `timeout.unref()` functions that can be used to
              * control this default behavior.
              */
-            class Timeout implements Timer {
-                /**
-                 * When called, requests that the Node.js event loop _not_ exit so long as the`Timeout` is active. Calling `timeout.ref()` multiple times will have no effect.
-                 *
-                 * By default, all `Timeout` objects are "ref'ed", making it normally unnecessary
-                 * to call `timeout.ref()` unless `timeout.unref()` had been called previously.
-                 * @since v0.9.1
-                 * @return a reference to `timeout`
-                 */
-                ref(): this;
+            interface Timeout extends RefCounted, Disposable, Timer {
                 /**
-                 * 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.
+                 * Cancels the timeout.
                  * @since v0.9.1
-                 * @return a reference to `timeout`
+                 * @legacy Use `clearTimeout()` instead.
+                 * @returns a reference to `timeout`
                  */
-                unref(): this;
+                close(): this;
                 /**
                  * If true, the `Timeout` object will keep the Node.js event loop active.
                  * @since v11.0.0
                  */
                 hasRef(): boolean;
+                /**
+                 * When called, requests that the Node.js event loop _not_ exit so long as the
+                 * `Timeout` is active. Calling `timeout.ref()` multiple times will have no effect.
+                 *
+                 * By default, all `Timeout` objects are "ref'ed", making it normally unnecessary
+                 * to call `timeout.ref()` unless `timeout.unref()` had been called previously.
+                 * @since v0.9.1
+                 * @returns a reference to `timeout`
+                 */
+                ref(): this;
                 /**
                  * Sets the timer's start time to the current time, and reschedules the timer to
                  * call its callback at the previously specified duration adjusted to the current
@@ -119,121 +116,171 @@ declare module "timers" {
                  * Using this on a timer that has already called its callback will reactivate the
                  * timer.
                  * @since v10.2.0
-                 * @return a reference to `timeout`
+                 * @returns a reference to `timeout`
                  */
                 refresh(): this;
+                /**
+                 * 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.
+                 * @since v0.9.1
+                 * @returns a reference to `timeout`
+                 */
+                unref(): this;
+                /**
+                 * Coerce a `Timeout` to a primitive. The primitive can be used to
+                 * clear the `Timeout`. The primitive can only be used in the
+                 * same thread where the timeout was created. Therefore, to use it
+                 * across `worker_threads` it must first be passed to the correct
+                 * thread. This allows enhanced compatibility with browser
+                 * `setTimeout()` and `setInterval()` implementations.
+                 * @since v14.9.0, v12.19.0
+                 */
                 [Symbol.toPrimitive](): number;
                 /**
                  * Cancels the timeout.
-                 * @since v20.5.0
+                 * @since v20.5.0, v18.18.0
+                 * @experimental
                  */
                 [Symbol.dispose](): void;
+                _onTimeout(...args: any[]): void;
             }
         }
         /**
-         * Schedules execution of a one-time `callback` after `delay` milliseconds.
-         *
-         * The `callback` will likely not be invoked in precisely `delay` milliseconds.
-         * Node.js makes no guarantees about the exact timing of when callbacks will fire,
-         * nor of their ordering. The callback will be called as close as possible to the
-         * time specified.
+         * Schedules the "immediate" execution of the `callback` after I/O events'
+         * callbacks.
          *
-         * 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 multiple calls to `setImmediate()` are made, the `callback` functions are
+         * queued for execution in the order in which they are created. The entire callback
+         * queue is processed every event loop iteration. If an immediate timer is queued
+         * from inside an executing callback, that timer will not be triggered until the
+         * next event loop iteration.
          *
          * If `callback` is not a function, a `TypeError` will be thrown.
          *
-         * This method has a custom variant for promises that is available using `timersPromises.setTimeout()`.
-         * @since v0.0.1
-         * @param callback The function to call when the timer elapses.
-         * @param [delay=1] The number of milliseconds to wait before calling the `callback`.
+         * This method has a custom variant for promises that is available using
+         * `timersPromises.setImmediate()`.
+         * @since v0.9.1
+         * @param callback The function to call at the end of this turn of
+         * the Node.js [Event Loop](https://nodejs.org/en/docs/guides/event-loop-timers-and-nexttick/#setimmediate-vs-settimeout)
          * @param args Optional arguments to pass when the `callback` is called.
-         * @return for use with {@link clearTimeout}
+         * @returns for use with `clearImmediate()`
          */
-        function setTimeout<TArgs extends any[]>(
+        function setImmediate<TArgs extends any[]>(
             callback: (...args: TArgs) => void,
-            ms?: number,
             ...args: TArgs
-        ): NodeJS.Timeout;
-        // util.promisify no rest args compability
+        ): NodeJS.Immediate;
+        // Allow a single void-accepting argument to be optional in arguments lists.
+        // Allows usage such as `new Promise(resolve => setTimeout(resolve, ms))` (#54258)
         // eslint-disable-next-line @typescript-eslint/no-invalid-void-type
-        function setTimeout(callback: (args: void) => void, ms?: number): NodeJS.Timeout;
-        namespace setTimeout {
-            const __promisify__: typeof setTimeoutPromise;
+        function setImmediate(callback: (_: void) => void): NodeJS.Immediate;
+        namespace setImmediate {
+            import __promisify__ = promises.setImmediate;
+            export { __promisify__ };
         }
-        /**
-         * Cancels a `Timeout` object created by `setTimeout()`.
-         * @since v0.0.1
-         * @param timeout A `Timeout` object as returned by {@link setTimeout} or the `primitive` of the `Timeout` object as a string or a number.
-         */
-        function clearTimeout(timeoutId: NodeJS.Timeout | string | number | undefined): void;
         /**
          * Schedules repeated execution of `callback` every `delay` milliseconds.
          *
-         * 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` or `NaN`, 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.
          *
-         * This method has a custom variant for promises that is available using `timersPromises.setInterval()`.
+         * This method has a custom variant for promises that is available using
+         * `timersPromises.setInterval()`.
          * @since v0.0.1
          * @param callback The function to call when the timer elapses.
-         * @param [delay=1] The number of milliseconds to wait before calling the `callback`.
+         * @param delay The number of milliseconds to wait before calling the
+         * `callback`. **Default:** `1`.
          * @param args Optional arguments to pass when the `callback` is called.
-         * @return for use with {@link clearInterval}
+         * @returns for use with `clearInterval()`
          */
         function setInterval<TArgs extends any[]>(
             callback: (...args: TArgs) => void,
-            ms?: number,
+            delay?: number,
             ...args: TArgs
         ): NodeJS.Timeout;
-        // util.promisify no rest args compability
+        // Allow a single void-accepting argument to be optional in arguments lists.
+        // Allows usage such as `new Promise(resolve => setTimeout(resolve, ms))` (#54258)
         // eslint-disable-next-line @typescript-eslint/no-invalid-void-type
-        function setInterval(callback: (args: void) => void, ms?: number): NodeJS.Timeout;
-        namespace setInterval {
-            const __promisify__: typeof setIntervalPromise;
-        }
-        /**
-         * Cancels a `Timeout` object created by `setInterval()`.
-         * @since v0.0.1
-         * @param timeout A `Timeout` object as returned by {@link setInterval} or the `primitive` of the `Timeout` object as a string or a number.
-         */
-        function clearInterval(intervalId: NodeJS.Timeout | string | number | undefined): void;
+        function setInterval(callback: (_: void) => void, delay?: number): NodeJS.Timeout;
         /**
-         * Schedules the "immediate" execution of the `callback` after I/O events'
-         * callbacks.
+         * Schedules execution of a one-time `callback` after `delay` milliseconds.
          *
-         * When multiple calls to `setImmediate()` are made, the `callback` functions are
-         * queued for execution in the order in which they are created. The entire callback
-         * queue is processed every event loop iteration. If an immediate timer is queued
-         * from inside an executing callback, that timer will not be triggered until the
-         * next event loop iteration.
+         * The `callback` will likely not be invoked in precisely `delay` milliseconds.
+         * Node.js makes no guarantees about the exact timing of when callbacks will fire,
+         * 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` or `NaN`, 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.
          *
-         * This method has a custom variant for promises that is available using `timersPromises.setImmediate()`.
-         * @since v0.9.1
-         * @param callback The function to call at the end of this turn of the Node.js `Event Loop`
+         * This method has a custom variant for promises that is available using
+         * `timersPromises.setTimeout()`.
+         * @since v0.0.1
+         * @param callback The function to call when the timer elapses.
+         * @param delay The number of milliseconds to wait before calling the
+         * `callback`. **Default:** `1`.
          * @param args Optional arguments to pass when the `callback` is called.
-         * @return for use with {@link clearImmediate}
+         * @returns for use with `clearTimeout()`
          */
-        function setImmediate<TArgs extends any[]>(
+        function setTimeout<TArgs extends any[]>(
             callback: (...args: TArgs) => void,
+            delay?: number,
             ...args: TArgs
-        ): NodeJS.Immediate;
-        // util.promisify no rest args compability
+        ): NodeJS.Timeout;
+        // Allow a single void-accepting argument to be optional in arguments lists.
+        // Allows usage such as `new Promise(resolve => setTimeout(resolve, ms))` (#54258)
         // eslint-disable-next-line @typescript-eslint/no-invalid-void-type
-        function setImmediate(callback: (args: void) => void): NodeJS.Immediate;
-        namespace setImmediate {
-            const __promisify__: typeof setImmediatePromise;
+        function setTimeout(callback: (_: void) => void, delay?: number): NodeJS.Timeout;
+        namespace setTimeout {
+            import __promisify__ = promises.setTimeout;
+            export { __promisify__ };
         }
         /**
          * Cancels an `Immediate` object created by `setImmediate()`.
          * @since v0.9.1
-         * @param immediate An `Immediate` object as returned by {@link setImmediate}.
+         * @param immediate An `Immediate` object as returned by `setImmediate()`.
+         */
+        function clearImmediate(immediate: NodeJS.Immediate | undefined): void;
+        /**
+         * Cancels a `Timeout` object created by `setInterval()`.
+         * @since v0.0.1
+         * @param timeout A `Timeout` object as returned by `setInterval()`
+         * or the primitive of the `Timeout` object as a string or a number.
+         */
+        function clearInterval(timeout: NodeJS.Timeout | string | number | undefined): void;
+        /**
+         * Cancels a `Timeout` object created by `setTimeout()`.
+         * @since v0.0.1
+         * @param timeout A `Timeout` object as returned by `setTimeout()`
+         * or the primitive of the `Timeout` object as a string or a number.
+         */
+        function clearTimeout(timeout: NodeJS.Timeout | string | number | undefined): void;
+        /**
+         * The `queueMicrotask()` method queues a microtask to invoke `callback`. If
+         * `callback` throws an exception, the `process` object `'uncaughtException'`
+         * event will be emitted.
+         *
+         * The microtask queue is managed by V8 and may be used in a similar manner to
+         * the `process.nextTick()` queue, which is managed by Node.js. The
+         * `process.nextTick()` queue is always processed before the microtask queue
+         * within each turn of the Node.js event loop.
+         * @since v11.0.0
+         * @param callback Function to be queued.
          */
-        function clearImmediate(immediateId: NodeJS.Immediate | undefined): void;
         function queueMicrotask(callback: () => void): void;
     }
+    import clearImmediate = globalThis.clearImmediate;
+    import clearInterval = globalThis.clearInterval;
+    import clearTimeout = globalThis.clearTimeout;
+    import setImmediate = globalThis.setImmediate;
+    import setInterval = globalThis.setInterval;
+    import setTimeout = globalThis.setTimeout;
+    export { clearImmediate, clearInterval, clearTimeout, promises, setImmediate, setInterval, setTimeout };
 }
 declare module "node:timers" {
     export * from "timers";

package/node_modules/@types/node/tls.d.ts

@@ -398,6 +398,14 @@ declare module "tls" {
             },
             callback: (err: Error | null) => void,
         ): undefined | boolean;
+        /**
+         * The `tlsSocket.setKeyCert()` method sets the private key and certificate to use for the socket.
+         * This is mainly useful if you wish to select a server certificate from a TLS server's `ALPNCallback`.
+         * @since v22.5.0, v20.17.0
+         * @param context An object containing at least `key` and `cert` properties from the {@link createSecureContext()} `options`,
+         * or a TLS context object created with {@link createSecureContext()} itself.
+         */
+        setKeyCert(context: SecureContextOptions | SecureContext): void;
         /**
          * The `tlsSocket.setMaxSendFragment()` method sets the maximum TLS fragment size.
          * Returns `true` if setting the limit succeeded; `false` otherwise.
@@ -639,7 +647,7 @@ declare module "tls" {
          * @param context An object containing any of the possible properties from the {@link createSecureContext} `options` arguments (e.g. `key`, `cert`, `ca`, etc), or a TLS context object created
          * with {@link createSecureContext} itself.
          */
-        addContext(hostname: string, context: SecureContextOptions): void;
+        addContext(hostname: string, context: SecureContextOptions | SecureContext): void;
         /**
          * Returns the session ticket keys.
          *
@@ -1158,6 +1166,31 @@ declare module "tls" {
      * @since v0.11.13
      */
     function createSecureContext(options?: SecureContextOptions): SecureContext;
+    /**
+     * Returns an array containing the CA certificates from various sources, depending on `type`:
+     *
+     * * `"default"`: return the CA certificates that will be used by the Node.js TLS clients by default.
+     *   * When `--use-bundled-ca` is enabled (default), or `--use-openssl-ca` is not enabled,
+     *     this would include CA certificates from the bundled Mozilla CA store.
+     *   * When `--use-system-ca` is enabled, this would also include certificates from the system's
+     *     trusted store.
+     *   * When `NODE_EXTRA_CA_CERTS` is used, this would also include certificates loaded from the specified
+     *     file.
+     * * `"system"`: return the CA certificates that are loaded from the system's trusted store, according
+     *   to rules set by `--use-system-ca`. This can be used to get the certificates from the system
+     *   when `--use-system-ca` is not enabled.
+     * * `"bundled"`: return the CA certificates from the bundled Mozilla CA store. This would be the same
+     *   as `tls.rootCertificates`.
+     * * `"extra"`: return the CA certificates loaded from `NODE_EXTRA_CA_CERTS`. It's an empty array if
+     *   `NODE_EXTRA_CA_CERTS` is not set.
+     * @since v22.15.0
+     * @param type The type of CA certificates that will be returned. Valid values
+     * are `"default"`, `"system"`, `"bundled"` and `"extra"`.
+     * **Default:** `"default"`.
+     * @returns An array of PEM-encoded certificates. The array may contain duplicates
+     * if the same certificate is repeatedly stored in multiple sources.
+     */
+    function getCACertificates(type?: "default" | "system" | "bundled" | "extra"): string[];
     /**
      * 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

package/node_modules/@types/node/ts5.6/buffer.buffer.d.ts

@@ -24,7 +24,7 @@ declare module "buffer" {
              * @param array The octets to store.
              * @deprecated since v10.0.0 - Use `Buffer.from(array)` instead.
              */
-            new(array: Uint8Array): Buffer;
+            new(array: ArrayLike<number>): Buffer;
             /**
              * Produces a Buffer backed by the same allocated memory as
              * the given {ArrayBuffer}/{SharedArrayBuffer}.
@@ -33,20 +33,6 @@ declare module "buffer" {
              * @deprecated since v10.0.0 - Use `Buffer.from(arrayBuffer[, byteOffset[, length]])` instead.
              */
             new(arrayBuffer: ArrayBuffer | SharedArrayBuffer): Buffer;
-            /**
-             * Allocates a new buffer containing the given {array} of octets.
-             *
-             * @param array The octets to store.
-             * @deprecated since v10.0.0 - Use `Buffer.from(array)` instead.
-             */
-            new(array: readonly any[]): Buffer;
-            /**
-             * Copies the passed {buffer} data onto a new {Buffer} instance.
-             *
-             * @param buffer The buffer to copy.
-             * @deprecated since v10.0.0 - Use `Buffer.from(buffer)` instead.
-             */
-            new(buffer: Buffer): Buffer;
             /**
              * Allocates a new `Buffer` using an `array` of bytes in the range `0` – `255`.
              * Array entries outside that range will be truncated to fit into it.
@@ -58,40 +44,121 @@ declare module "buffer" {
              * const buf = Buffer.from([0x62, 0x75, 0x66, 0x66, 0x65, 0x72]);
              * ```
              *
-             * If `array` is an `Array`\-like object (that is, one with a `length` property of
+             * If `array` is an `Array`-like object (that is, one with a `length` property of
              * type `number`), it is treated as if it is an array, unless it is a `Buffer` or
-             * a `Uint8Array`. This means all other `TypedArray` variants get treated as an `Array`. To create a `Buffer` from the bytes backing a `TypedArray`, use `Buffer.copyBytesFrom()`.
+             * a `Uint8Array`. This means all other `TypedArray` variants get treated as an
+             * `Array`. To create a `Buffer` from the bytes backing a `TypedArray`, use
+             * `Buffer.copyBytesFrom()`.
              *
              * A `TypeError` will be thrown if `array` is not an `Array` or another type
              * appropriate for `Buffer.from()` variants.
              *
-             * `Buffer.from(array)` and `Buffer.from(string)` may also use the internal `Buffer` pool like `Buffer.allocUnsafe()` does.
+             * `Buffer.from(array)` and `Buffer.from(string)` may also use the internal
+             * `Buffer` pool like `Buffer.allocUnsafe()` does.
              * @since v5.10.0
              */
+            from(array: WithImplicitCoercion<ArrayLike<number>>): Buffer;
+            /**
+             * This creates a view of the `ArrayBuffer` without copying the underlying
+             * memory. For example, when passed a reference to the `.buffer` property of a
+             * `TypedArray` instance, the newly created `Buffer` will share the same
+             * allocated memory as the `TypedArray`'s underlying `ArrayBuffer`.
+             *
+             * ```js
+             * import { Buffer } from 'node:buffer';
+             *
+             * const arr = new Uint16Array(2);
+             *
+             * arr[0] = 5000;
+             * arr[1] = 4000;
+             *
+             * // Shares memory with `arr`.
+             * const buf = Buffer.from(arr.buffer);
+             *
+             * console.log(buf);
+             * // Prints: <Buffer 88 13 a0 0f>
+             *
+             * // Changing the original Uint16Array changes the Buffer also.
+             * arr[1] = 6000;
+             *
+             * console.log(buf);
+             * // Prints: <Buffer 88 13 70 17>
+             * ```
+             *
+             * The optional `byteOffset` and `length` arguments specify a memory range within
+             * the `arrayBuffer` that will be shared by the `Buffer`.
+             *
+             * ```js
+             * import { Buffer } from 'node:buffer';
+             *
+             * const ab = new ArrayBuffer(10);
+             * const buf = Buffer.from(ab, 0, 2);
+             *
+             * console.log(buf.length);
+             * // Prints: 2
+             * ```
+             *
+             * A `TypeError` will be thrown if `arrayBuffer` is not an `ArrayBuffer` or a
+             * `SharedArrayBuffer` or another type appropriate for `Buffer.from()`
+             * variants.
+             *
+             * It is important to remember that a backing `ArrayBuffer` can cover a range
+             * of memory that extends beyond the bounds of a `TypedArray` view. A new
+             * `Buffer` created using the `buffer` property of a `TypedArray` may extend
+             * beyond the range of the `TypedArray`:
+             *
+             * ```js
+             * import { Buffer } from 'node:buffer';
+             *
+             * const arrA = Uint8Array.from([0x63, 0x64, 0x65, 0x66]); // 4 elements
+             * const arrB = new Uint8Array(arrA.buffer, 1, 2); // 2 elements
+             * console.log(arrA.buffer === arrB.buffer); // true
+             *
+             * const buf = Buffer.from(arrB.buffer);
+             * console.log(buf);
+             * // Prints: <Buffer 63 64 65 66>
+             * ```
+             * @since v5.10.0
+             * @param arrayBuffer An `ArrayBuffer`, `SharedArrayBuffer`, for example the
+             * `.buffer` property of a `TypedArray`.
+             * @param byteOffset Index of first byte to expose. **Default:** `0`.
+             * @param length Number of bytes to expose. **Default:**
+             * `arrayBuffer.byteLength - byteOffset`.
+             */
             from(
                 arrayBuffer: WithImplicitCoercion<ArrayBuffer | SharedArrayBuffer>,
                 byteOffset?: number,
                 length?: number,
             ): Buffer;
             /**
-             * Creates a new Buffer using the passed {data}
-             * @param data data to create a new Buffer
-             */
-            from(data: Uint8Array | readonly number[]): Buffer;
-            from(data: WithImplicitCoercion<Uint8Array | readonly number[] | string>): Buffer;
-            /**
-             * Creates a new Buffer containing the given JavaScript string {str}.
-             * If provided, the {encoding} parameter identifies the character encoding.
-             * If not provided, {encoding} defaults to 'utf8'.
+             * Creates a new `Buffer` containing `string`. The `encoding` parameter identifies
+             * the character encoding to be used when converting `string` into bytes.
+             *
+             * ```js
+             * import { Buffer } from 'node:buffer';
+             *
+             * const buf1 = Buffer.from('this is a tést');
+             * const buf2 = Buffer.from('7468697320697320612074c3a97374', 'hex');
+             *
+             * console.log(buf1.toString());
+             * // Prints: this is a tést
+             * console.log(buf2.toString());
+             * // Prints: this is a tést
+             * console.log(buf1.toString('latin1'));
+             * // Prints: this is a tést
+             * ```
+             *
+             * A `TypeError` will be thrown if `string` is not a string or another type
+             * appropriate for `Buffer.from()` variants.
+             *
+             * `Buffer.from(string)` may also use the internal `Buffer` pool like
+             * `Buffer.allocUnsafe()` does.
+             * @since v5.10.0
+             * @param string A string to encode.
+             * @param encoding The encoding of `string`. **Default:** `'utf8'`.
              */
-            from(
-                str:
-                    | WithImplicitCoercion<string>
-                    | {
-                        [Symbol.toPrimitive](hint: "string"): string;
-                    },
-                encoding?: BufferEncoding,
-            ): Buffer;
+            from(string: WithImplicitCoercion<string>, encoding?: BufferEncoding): Buffer;
+            from(arrayOrString: WithImplicitCoercion<ArrayLike<number> | string>): Buffer;
             /**
              * Creates a new Buffer using the passed {data}
              * @param values to create a new Buffer
@@ -381,5 +448,13 @@ declare module "buffer" {
              */
             subarray(start?: number, end?: number): Buffer;
         }
+        type NonSharedBuffer = Buffer;
+        type AllowSharedBuffer = Buffer;
     }
+    /** @deprecated Use `Buffer.allocUnsafeSlow()` instead. */
+    var SlowBuffer: {
+        /** @deprecated Use `Buffer.allocUnsafeSlow()` instead. */
+        new(size: number): Buffer;
+        prototype: Buffer;
+    };
 }