@types/node 20.9.2 → 20.9.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
node/worker_threads.d.ts CHANGED
@@ -173,7 +173,7 @@ declare module "worker_threads" {
173
173
  * behind this API, see the `serialization API of the node:v8 module`.
174
174
  * @since v10.5.0
175
175
  */
176
- postMessage(value: any, transferList?: ReadonlyArray<TransferListItem>): void;
176
+ postMessage(value: any, transferList?: readonly TransferListItem[]): void;
177
177
  /**
178
178
  * Opposite of `unref()`. Calling `ref()` on a previously `unref()`ed port does _not_ let the program exit if it's the only active handle left (the default
179
179
  * behavior). If the port is `ref()`ed, calling `ref()` again has no effect.
@@ -405,7 +405,7 @@ declare module "worker_threads" {
405
405
  * See `port.postMessage()` for more details.
406
406
  * @since v10.5.0
407
407
  */
408
- postMessage(value: any, transferList?: ReadonlyArray<TransferListItem>): void;
408
+ postMessage(value: any, transferList?: readonly TransferListItem[]): void;
409
409
  /**
410
410
  * Opposite of `unref()`, calling `ref()` on a previously `unref()`ed worker does _not_ let the program exit if it's the only active handle left (the default
411
411
  * behavior). If the worker is `ref()`ed, calling `ref()` again has