cdk-common 2.1.11 → 2.1.13

package/node_modules/@types/form-data/node_modules/@types/node/punycode.d.ts

@@ -1,31 +1,3 @@
-/**
- * **The version of the punycode module bundled in Node.js is being deprecated. **In a future major version of Node.js this module will be removed. Users
- * currently depending on the `punycode` module should switch to using the
- * userland-provided [Punycode.js](https://github.com/bestiejs/punycode.js) module instead. For punycode-based URL
- * encoding, see `url.domainToASCII` or, more generally, the `WHATWG URL API`.
- *
- * The `punycode` module is a bundled version of the [Punycode.js](https://github.com/bestiejs/punycode.js) module. It
- * can be accessed using:
- *
- * ```js
- * import punycode from 'node:punycode';
- * ```
- *
- * [Punycode](https://tools.ietf.org/html/rfc3492) is a character encoding scheme defined by RFC 3492 that is
- * primarily intended for use in Internationalized Domain Names. Because host
- * names in URLs are limited to ASCII characters only, Domain Names that contain
- * non-ASCII characters must be converted into ASCII using the Punycode scheme.
- * For instance, the Japanese character that translates into the English word, `'example'` is `'例'`. The Internationalized Domain Name, `'例.com'` (equivalent
- * to `'example.com'`) is represented by Punycode as the ASCII string `'xn--fsq.com'`.
- *
- * The `punycode` module provides a simple implementation of the Punycode standard.
- *
- * The `punycode` module is a third-party dependency used by Node.js and
- * made available to developers as a convenience. Fixes or other modifications to
- * the module must be directed to the [Punycode.js](https://github.com/bestiejs/punycode.js) project.
- * @deprecated
- * @see [source](https://github.com/nodejs/node/blob/v25.x/lib/punycode.js)
- */
 declare module "node:punycode" {
     /**
      * The `punycode.decode()` method converts a [Punycode](https://tools.ietf.org/html/rfc3492) string of ASCII-only

package/node_modules/@types/form-data/node_modules/@types/node/querystring.d.ts

@@ -1,16 +1,3 @@
-/**
- * The `node:querystring` module provides utilities for parsing and formatting URL
- * query strings. It can be accessed using:
- *
- * ```js
- * import querystring from 'node:querystring';
- * ```
- *
- * `querystring` is more performant than `URLSearchParams` but is not a
- * standardized API. Use `URLSearchParams` when performance is not critical or
- * when compatibility with browser code is desirable.
- * @see [source](https://github.com/nodejs/node/blob/v25.x/lib/querystring.js)
- */
 declare module "node:querystring" {
     interface StringifyOptions {
         /**

package/node_modules/@types/form-data/node_modules/@types/node/quic.d.ts

@@ -1,16 +1,3 @@
-/**
- * The 'node:quic' module provides an implementation of the QUIC protocol.
- * To access it, start Node.js with the `--experimental-quic` option and:
- *
- * ```js
- * import quic from 'node:quic';
- * ```
- *
- * The module is only available under the `node:` scheme.
- * @since v23.8.0
- * @experimental
- * @see [source](https://github.com/nodejs/node/blob/v25.x/lib/quic.js)
- */
 declare module "node:quic" {
     import { KeyObject, webcrypto } from "node:crypto";
     import { SocketAddress } from "node:net";

package/node_modules/@types/form-data/node_modules/@types/node/readline/promises.d.ts

@@ -1,6 +1,3 @@
-/**
- * @since v17.0.0
- */
 declare module "node:readline/promises" {
     import { Abortable } from "node:events";
     import {

package/node_modules/@types/form-data/node_modules/@types/node/readline.d.ts

@@ -1,38 +1,3 @@
-/**
- * The `node:readline` module provides an interface for reading data from a [Readable](https://nodejs.org/docs/latest-v25.x/api/stream.html#readable-streams) stream
- * (such as [`process.stdin`](https://nodejs.org/docs/latest-v25.x/api/process.html#processstdin)) one line at a time.
- *
- * To use the promise-based APIs:
- *
- * ```js
- * import * as readline from 'node:readline/promises';
- * ```
- *
- * To use the callback and sync APIs:
- *
- * ```js
- * import * as readline from 'node:readline';
- * ```
- *
- * The following simple example illustrates the basic use of the `node:readline` module.
- *
- * ```js
- * import * as readline from 'node:readline/promises';
- * import { stdin as input, stdout as output } from 'node:process';
- *
- * const rl = readline.createInterface({ input, output });
- *
- * const answer = await rl.question('What do you think of Node.js? ');
- *
- * console.log(`Thank you for your valuable feedback: ${answer}`);
- *
- * rl.close();
- * ```
- *
- * Once this code is invoked, the Node.js application will not terminate until the `readline.Interface` is closed because the interface waits for data to be
- * received on the `input` stream.
- * @see [source](https://github.com/nodejs/node/blob/v25.x/lib/readline.js)
- */
 declare module "node:readline" {
     import { Abortable, EventEmitter, InternalEventEmitter } from "node:events";
     interface Key {

package/node_modules/@types/form-data/node_modules/@types/node/repl.d.ts

@@ -1,13 +1,3 @@
-/**
- * The `node:repl` module provides a Read-Eval-Print-Loop (REPL) implementation
- * that is available both as a standalone program or includible in other
- * applications. It can be accessed using:
- *
- * ```js
- * import repl from 'node:repl';
- * ```
- * @see [source](https://github.com/nodejs/node/blob/v25.x/lib/repl.js)
- */
 declare module "node:repl" {
     import { AsyncCompleter, Completer, Interface, InterfaceEventMap } from "node:readline";
     import { InspectOptions } from "node:util";

package/node_modules/@types/form-data/node_modules/@types/node/sea.d.ts

@@ -1,118 +1,3 @@
-/**
- * This feature allows the distribution of a Node.js application conveniently to a
- * system that does not have Node.js installed.
- *
- * Node.js supports the creation of [single executable applications](https://github.com/nodejs/single-executable) by allowing
- * the injection of a blob prepared by Node.js, which can contain a bundled script,
- * into the `node` binary. During start up, the program checks if anything has been
- * injected. If the blob is found, it executes the script in the blob. Otherwise
- * Node.js operates as it normally does.
- *
- * The single executable application feature currently only supports running a
- * single embedded script using the `CommonJS` module system.
- *
- * Users can create a single executable application from their bundled script
- * with the `node` binary itself and any tool which can inject resources into the
- * binary.
- *
- * Here are the steps for creating a single executable application using one such
- * tool, [postject](https://github.com/nodejs/postject):
- *
- * 1. Create a JavaScript file:
- * ```bash
- * echo 'console.log(`Hello, ${process.argv[2]}!`);' > hello.js
- * ```
- * 2. Create a configuration file building a blob that can be injected into the
- * single executable application (see `Generating single executable preparation blobs` for details):
- * ```bash
- * echo '{ "main": "hello.js", "output": "sea-prep.blob" }' > sea-config.json
- * ```
- * 3. Generate the blob to be injected:
- * ```bash
- * node --experimental-sea-config sea-config.json
- * ```
- * 4. Create a copy of the `node` executable and name it according to your needs:
- *    * On systems other than Windows:
- * ```bash
- * cp $(command -v node) hello
- * ```
- *    * On Windows:
- * ```text
- * node -e "require('fs').copyFileSync(process.execPath, 'hello.exe')"
- * ```
- * The `.exe` extension is necessary.
- * 5. Remove the signature of the binary (macOS and Windows only):
- *    * On macOS:
- * ```bash
- * codesign --remove-signature hello
- * ```
- *    * On Windows (optional):
- * [signtool](https://learn.microsoft.com/en-us/windows/win32/seccrypto/signtool) can be used from the installed [Windows SDK](https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/).
- * If this step is
- * skipped, ignore any signature-related warning from postject.
- * ```powershell
- * signtool remove /s hello.exe
- * ```
- * 6. Inject the blob into the copied binary by running `postject` with
- * the following options:
- *    * `hello` / `hello.exe` \- The name of the copy of the `node` executable
- *    created in step 4.
- *    * `NODE_SEA_BLOB` \- The name of the resource / note / section in the binary
- *    where the contents of the blob will be stored.
- *    * `sea-prep.blob` \- The name of the blob created in step 1.
- *    * `--sentinel-fuse NODE_SEA_FUSE_fce680ab2cc467b6e072b8b5df1996b2` \- The [fuse](https://www.electronjs.org/docs/latest/tutorial/fuses) used by the Node.js project to detect if a file has been
- * injected.
- *    * `--macho-segment-name NODE_SEA` (only needed on macOS) - The name of the
- *    segment in the binary where the contents of the blob will be
- *    stored.
- * To summarize, here is the required command for each platform:
- *    * On Linux:
- *    ```bash
- *    npx postject hello NODE_SEA_BLOB sea-prep.blob \
- *        --sentinel-fuse NODE_SEA_FUSE_fce680ab2cc467b6e072b8b5df1996b2
- *    ```
- *    * On Windows - PowerShell:
- *    ```powershell
- *    npx postject hello.exe NODE_SEA_BLOB sea-prep.blob `
- *        --sentinel-fuse NODE_SEA_FUSE_fce680ab2cc467b6e072b8b5df1996b2
- *    ```
- *    * On Windows - Command Prompt:
- *    ```text
- *    npx postject hello.exe NODE_SEA_BLOB sea-prep.blob ^
- *        --sentinel-fuse NODE_SEA_FUSE_fce680ab2cc467b6e072b8b5df1996b2
- *    ```
- *    * On macOS:
- *    ```bash
- *    npx postject hello NODE_SEA_BLOB sea-prep.blob \
- *        --sentinel-fuse NODE_SEA_FUSE_fce680ab2cc467b6e072b8b5df1996b2 \
- *        --macho-segment-name NODE_SEA
- *    ```
- * 7. Sign the binary (macOS and Windows only):
- *    * On macOS:
- * ```bash
- * codesign --sign - hello
- * ```
- *    * On Windows (optional):
- * A certificate needs to be present for this to work. However, the unsigned
- * binary would still be runnable.
- * ```powershell
- * signtool sign /fd SHA256 hello.exe
- * ```
- * 8. Run the binary:
- *    * On systems other than Windows
- * ```console
- * $ ./hello world
- * Hello, world!
- * ```
- *    * On Windows
- * ```console
- * $ .\hello.exe world
- * Hello, world!
- * ```
- * @since v19.7.0, v18.16.0
- * @experimental
- * @see [source](https://github.com/nodejs/node/blob/v25.x/src/node_sea.cc)
- */
 declare module "node:sea" {
     type AssetKey = string;
     /**

package/node_modules/@types/form-data/node_modules/@types/node/sqlite.d.ts

@@ -1,47 +1,3 @@
-/**
- * The `node:sqlite` module facilitates working with SQLite databases.
- * To access it:
- *
- * ```js
- * import sqlite from 'node:sqlite';
- * ```
- *
- * This module is only available under the `node:` scheme. The following will not
- * work:
- *
- * ```js
- * import sqlite from 'sqlite';
- * ```
- *
- * The following example shows the basic usage of the `node:sqlite` module to open
- * an in-memory database, write data to the database, and then read the data back.
- *
- * ```js
- * import { DatabaseSync } from 'node:sqlite';
- * const database = new DatabaseSync(':memory:');
- *
- * // Execute SQL statements from strings.
- * database.exec(`
- *   CREATE TABLE data(
- *     key INTEGER PRIMARY KEY,
- *     value TEXT
- *   ) STRICT
- * `);
- * // Create a prepared statement to insert data into the database.
- * const insert = database.prepare('INSERT INTO data (key, value) VALUES (?, ?)');
- * // Execute the prepared statement with bound values.
- * insert.run(1, 'hello');
- * insert.run(2, 'world');
- * // Create a prepared statement to read data from the database.
- * const query = database.prepare('SELECT * FROM data ORDER BY key');
- * // Execute the prepared statement and log the result set.
- * console.log(query.all());
- * // Prints: [ { key: 1, value: 'hello' }, { key: 2, value: 'world' } ]
- * ```
- * @since v22.5.0
- * @experimental
- * @see [source](https://github.com/nodejs/node/blob/v25.x/lib/sqlite.js)
- */
 declare module "node:sqlite" {
     import { PathLike } from "node:fs";
     type SQLInputValue = null | number | bigint | string | NodeJS.ArrayBufferView;

package/node_modules/@types/form-data/node_modules/@types/node/stream/consumers.d.ts

@@ -1,33 +1,109 @@
-/**
- * The utility consumer functions provide common options for consuming
- * streams.
- * @since v16.7.0
- */
 declare module "node:stream/consumers" {
     import { Blob, NonSharedBuffer } from "node:buffer";
     import { ReadableStream } from "node:stream/web";
     /**
+     * ```js
+     * import { arrayBuffer } from 'node:stream/consumers';
+     * import { Readable } from 'node:stream';
+     * import { TextEncoder } from 'node:util';
+     *
+     * const encoder = new TextEncoder();
+     * const dataArray = encoder.encode('hello world from consumers!');
+     *
+     * const readable = Readable.from(dataArray);
+     * const data = await arrayBuffer(readable);
+     * console.log(`from readable: ${data.byteLength}`);
+     * // Prints: from readable: 76
+     * ```
      * @since v16.7.0
      * @returns Fulfills with an `ArrayBuffer` containing the full contents of the stream.
      */
     function arrayBuffer(stream: ReadableStream | NodeJS.ReadableStream | AsyncIterable<any>): Promise<ArrayBuffer>;
     /**
+     * ```js
+     * import { blob } from 'node:stream/consumers';
+     *
+     * const dataBlob = new Blob(['hello world from consumers!']);
+     *
+     * const readable = dataBlob.stream();
+     * const data = await blob(readable);
+     * console.log(`from readable: ${data.size}`);
+     * // Prints: from readable: 27
+     * ```
      * @since v16.7.0
      * @returns Fulfills with a `Blob` containing the full contents of the stream.
      */
     function blob(stream: ReadableStream | NodeJS.ReadableStream | AsyncIterable<any>): Promise<Blob>;
     /**
+     * ```js
+     * import { buffer } from 'node:stream/consumers';
+     * import { Readable } from 'node:stream';
+     * import { Buffer } from 'node:buffer';
+     *
+     * const dataBuffer = Buffer.from('hello world from consumers!');
+     *
+     * const readable = Readable.from(dataBuffer);
+     * const data = await buffer(readable);
+     * console.log(`from readable: ${data.length}`);
+     * // Prints: from readable: 27
+     * ```
      * @since v16.7.0
      * @returns Fulfills with a `Buffer` containing the full contents of the stream.
      */
     function buffer(stream: ReadableStream | NodeJS.ReadableStream | AsyncIterable<any>): Promise<NonSharedBuffer>;
     /**
+     * ```js
+     * import { bytes } from 'node:stream/consumers';
+     * import { Readable } from 'node:stream';
+     * import { Buffer } from 'node:buffer';
+     *
+     * const dataBuffer = Buffer.from('hello world from consumers!');
+     *
+     * const readable = Readable.from(dataBuffer);
+     * const data = await bytes(readable);
+     * console.log(`from readable: ${data.length}`);
+     * // Prints: from readable: 27
+     * ```
+     * @since v25.6.0
+     * @returns Fulfills with a `Uint8Array` containing the full contents of the stream.
+     */
+    function bytes(
+        stream: ReadableStream | NodeJS.ReadableStream | AsyncIterable<any>,
+    ): Promise<NodeJS.NonSharedUint8Array>;
+    /**
+     * ```js
+     * import { json } from 'node:stream/consumers';
+     * import { Readable } from 'node:stream';
+     *
+     * const items = Array.from(
+     *   {
+     *     length: 100,
+     *   },
+     *   () => ({
+     *     message: 'hello world from consumers!',
+     *   }),
+     * );
+     *
+     * const readable = Readable.from(JSON.stringify(items));
+     * const data = await json(readable);
+     * console.log(`from readable: ${data.length}`);
+     * // Prints: from readable: 100
+     * ```
      * @since v16.7.0
      * @returns Fulfills with the contents of the stream parsed as a
      * UTF-8 encoded string that is then passed through `JSON.parse()`.
      */
     function json(stream: ReadableStream | NodeJS.ReadableStream | AsyncIterable<any>): Promise<unknown>;
     /**
+     * ```js
+     * import { text } from 'node:stream/consumers';
+     * import { Readable } from 'node:stream';
+     *
+     * const readable = Readable.from('Hello world from consumers!');
+     * const data = await text(readable);
+     * console.log(`from readable: ${data.length}`);
+     * // Prints: from readable: 27
+     * ```
      * @since v16.7.0
      * @returns Fulfills with the contents of the stream parsed as a UTF-8 encoded string.
      */

package/node_modules/@types/form-data/node_modules/@types/node/stream/web.d.ts

@@ -206,7 +206,7 @@ declare module "node:stream/web" {
     interface ReadableStreamDefaultController<R = any> {
         readonly desiredSize: number | null;
         close(): void;
-        enqueue(chunk?: R): void;
+        enqueue(chunk: R): void;
         error(e?: any): void;
     }
     var ReadableStreamDefaultController: {
@@ -251,7 +251,7 @@ declare module "node:stream/web" {
     };
     interface TransformStreamDefaultController<O = any> {
         readonly desiredSize: number | null;
-        enqueue(chunk?: O): void;
+        enqueue(chunk: O): void;
         error(reason?: any): void;
         terminate(): void;
     }
@@ -284,7 +284,7 @@ declare module "node:stream/web" {
         abort(reason?: any): Promise<void>;
         close(): Promise<void>;
         releaseLock(): void;
-        write(chunk?: W): Promise<void>;
+        write(chunk: W): Promise<void>;
     }
     var WritableStreamDefaultWriter: {
         prototype: WritableStreamDefaultWriter;

package/node_modules/@types/form-data/node_modules/@types/node/stream.d.ts

@@ -1,22 +1,3 @@
-/**
- * A stream is an abstract interface for working with streaming data in Node.js.
- * The `node:stream` module provides an API for implementing the stream interface.
- *
- * There are many stream objects provided by Node.js. For instance, a [request to an HTTP server](https://nodejs.org/docs/latest-v25.x/api/http.html#class-httpincomingmessage)
- * and [`process.stdout`](https://nodejs.org/docs/latest-v25.x/api/process.html#processstdout) are both stream instances.
- *
- * Streams can be readable, writable, or both. All streams are instances of [`EventEmitter`](https://nodejs.org/docs/latest-v25.x/api/events.html#class-eventemitter).
- *
- * To access the `node:stream` module:
- *
- * ```js
- * import stream from 'node:stream';
- * ```
- *
- * The `node:stream` module is useful for creating new types of stream instances.
- * It is usually not necessary to use the `node:stream` module to consume streams.
- * @see [source](https://github.com/nodejs/node/blob/v25.x/lib/stream.js)
- */
 declare module "node:stream" {
     import { Blob } from "node:buffer";
     import { Abortable, EventEmitter } from "node:events";
@@ -899,11 +880,20 @@ declare module "node:stream" {
              * @since v0.9.4
              * @param chunk Optional data to write. For streams not operating in object mode, `chunk` must be a {string}, {Buffer},
              * {TypedArray} or {DataView}. For object mode streams, `chunk` may be any JavaScript value other than `null`.
-             * @param [encoding='utf8'] The encoding, if `chunk` is a string.
              * @param callback Callback for when this chunk of data is flushed.
              * @return `false` if the stream wishes for the calling code to wait for the `'drain'` event to be emitted before continuing to write additional data; otherwise `true`.
              */
             write(chunk: any, callback?: (error: Error | null | undefined) => void): boolean;
+            /**
+             * Writes data to the stream, with an explicit encoding for string data.
+             * @see {@link Writable.write} for full details.
+             * @since v0.9.4
+             * @param chunk Optional data to write. For streams not operating in object mode, `chunk` must be a {string}, {Buffer},
+             * {TypedArray} or {DataView}. For object mode streams, `chunk` may be any JavaScript value other than `null`.
+             * @param encoding The encoding, if `chunk` is a string.
+             * @param callback Callback for when this chunk of data is flushed.
+             * @return `false` if the stream wishes for the calling code to wait for the `'drain'` event to be emitted before continuing to write additional data; otherwise `true`.
+             */
             write(chunk: any, encoding: BufferEncoding, callback?: (error: Error | null | undefined) => void): boolean;
             /**
              * The `writable.setDefaultEncoding()` method sets the default `encoding` for a `Writable` stream.
@@ -928,13 +918,27 @@ declare module "node:stream" {
              * // Writing more now is not allowed!
              * ```
              * @since v0.9.4
+             * @param cb Callback for when the stream is finished.
+             */
+            end(cb?: () => void): this;
+            /**
+             * Signals that no more data will be written, with one final chunk of data.
+             * @see {@link Writable.end} for full details.
+             * @since v0.9.4
              * @param chunk Optional data to write. For streams not operating in object mode, `chunk` must be a {string}, {Buffer},
              * {TypedArray} or {DataView}. For object mode streams, `chunk` may be any JavaScript value other than `null`.
-             * @param encoding The encoding if `chunk` is a string
-             * @param callback Callback for when the stream is finished.
+             * @param cb Callback for when the stream is finished.
              */
-            end(cb?: () => void): this;
             end(chunk: any, cb?: () => void): this;
+            /**
+             * Signals that no more data will be written, with one final chunk of data.
+             * @see {@link Writable.end} for full details.
+             * @since v0.9.4
+             * @param chunk Optional data to write. For streams not operating in object mode, `chunk` must be a {string}, {Buffer},
+             * {TypedArray} or {DataView}. For object mode streams, `chunk` may be any JavaScript value other than `null`.
+             * @param encoding The encoding if `chunk` is a string
+             * @param cb Callback for when the stream is finished.
+             */
             end(chunk: any, encoding: BufferEncoding, cb?: () => void): this;
             /**
              * The `writable.cork()` method forces all written data to be buffered in memory.

package/node_modules/@types/form-data/node_modules/@types/node/string_decoder.d.ts

@@ -1,43 +1,3 @@
-/**
- * The `node:string_decoder` module provides an API for decoding `Buffer` objects
- * into strings in a manner that preserves encoded multi-byte UTF-8 and UTF-16
- * characters. It can be accessed using:
- *
- * ```js
- * import { StringDecoder } from 'node:string_decoder';
- * ```
- *
- * The following example shows the basic use of the `StringDecoder` class.
- *
- * ```js
- * import { StringDecoder } from 'node:string_decoder';
- * const decoder = new StringDecoder('utf8');
- *
- * const cent = Buffer.from([0xC2, 0xA2]);
- * console.log(decoder.write(cent)); // Prints: ¢
- *
- * const euro = Buffer.from([0xE2, 0x82, 0xAC]);
- * console.log(decoder.write(euro)); // Prints: €
- * ```
- *
- * When a `Buffer` instance is written to the `StringDecoder` instance, an
- * internal buffer is used to ensure that the decoded string does not contain
- * any incomplete multibyte characters. These are held in the buffer until the
- * next call to `stringDecoder.write()` or until `stringDecoder.end()` is called.
- *
- * In the following example, the three UTF-8 encoded bytes of the European Euro
- * symbol (`€`) are written over three separate operations:
- *
- * ```js
- * import { StringDecoder } from 'node:string_decoder';
- * const decoder = new StringDecoder('utf8');
- *
- * decoder.write(Buffer.from([0xE2]));
- * decoder.write(Buffer.from([0x82]));
- * console.log(decoder.end(Buffer.from([0xAC]))); // Prints: €
- * ```
- * @see [source](https://github.com/nodejs/node/blob/v25.x/lib/string_decoder.js)
- */
 declare module "node:string_decoder" {
     class StringDecoder {
         constructor(encoding?: BufferEncoding);

package/node_modules/@types/form-data/node_modules/@types/node/test/reporters.d.ts

@@ -1,41 +1,3 @@
-/**
- * The `node:test` module supports passing `--test-reporter`
- * flags for the test runner to use a specific reporter.
- *
- * The following built-reporters are supported:
- *
- * * `spec`
- *   The `spec` reporter outputs the test results in a human-readable format. This
- *   is the default reporter.
- *
- * * `tap`
- *   The `tap` reporter outputs the test results in the [TAP](https://testanything.org/) format.
- *
- * * `dot`
- *   The `dot` reporter outputs the test results in a compact format,
- *   where each passing test is represented by a `.`,
- *   and each failing test is represented by a `X`.
- *
- * * `junit`
- *   The junit reporter outputs test results in a jUnit XML format
- *
- * * `lcov`
- *   The `lcov` reporter outputs test coverage when used with the
- *   `--experimental-test-coverage` flag.
- *
- * The exact output of these reporters is subject to change between versions of
- * Node.js, and should not be relied on programmatically. If programmatic access
- * to the test runner's output is required, use the events emitted by the
- * `TestsStream`.
- *
- * The reporters are available via the `node:test/reporters` module:
- *
- * ```js
- * import { tap, spec, dot, junit, lcov } from 'node:test/reporters';
- * ```
- * @since v19.9.0, v18.17.0
- * @see [source](https://github.com/nodejs/node/blob/v25.x/lib/test/reporters.js)
- */
 declare module "node:test/reporters" {
     import { Transform, TransformOptions } from "node:stream";
     import { EventData } from "node:test";