@overdeck/desktop 0.50.0 → 0.50.3

package/server/node_modules/@types/node/trace_events.d.ts

@@ -1,4 +1,98 @@
-declare module "node:trace_events" {
+/**
+ * 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 `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`](https://nodejs.org/docs/latest-v22.x/api/async_hooks.html) trace data.
+ * The [`async_hooks`](https://nodejs.org/docs/latest-v22.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.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.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](https://nodejs.org/docs/latest-v22.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](https://nodejs.org/docs/latest-v22.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.
+ *
+ * ```bash
+ * 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.
+ *
+ * ```bash
+ * node --trace-events-enabled
+ *
+ * # is equivalent to
+ *
+ * node --trace-event-categories v8,node,node.async_hooks
+ * ```
+ *
+ * Alternatively, trace events may be enabled using the `node:trace_events` module:
+ *
+ * ```js
+ * import trace_events from 'node:trace_events';
+ * const tracing = trace_events.createTracing({ categories: ['node.perf'] });
+ * tracing.enable();  // Enable trace event capture for the 'node.perf' category
+ *
+ * // do work
+ *
+ * tracing.disable();  // Disable trace event capture for the 'node.perf' category
+ * ```
+ *
+ * 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
+ * be specified with `--trace-event-file-pattern` that accepts a template
+ * string that supports `${rotation}` and `${pid}`:
+ *
+ * ```bash
+ * 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
+ * in your code, such as:
+ *
+ * ```js
+ * process.on('SIGINT', function onSigint() {
+ *   console.info('Received SIGINT.');
+ *   process.exit(130);  // Or applicable exit code depending on OS and signal
+ * });
+ * ```
+ *
+ * The tracing system uses the same time source
+ * as the one used by `process.hrtime()`.
+ * 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`](https://nodejs.org/docs/latest-v22.x/api/worker_threads.html#class-worker) threads.
+ * @experimental
+ * @see [source](https://github.com/nodejs/node/blob/v22.x/lib/trace_events.js)
+ */
+declare module "trace_events" {
     /**
      * The `Tracing` object is used to enable or disable tracing for sets of
      * categories. Instances are created using the
@@ -98,6 +192,6 @@ declare module "node:trace_events" {
      */
     function getEnabledCategories(): string | undefined;
 }
-declare module "trace_events" {
-    export * from "node:trace_events";
+declare module "node:trace_events" {
+    export * from "trace_events";
 }

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

@@ -1,4 +1,4 @@
-declare module "node:buffer" {
+declare module "buffer" {
     global {
         interface BufferConstructor {
             // see ../buffer.d.ts for implementation shared with all TypeScript versions
@@ -172,7 +172,7 @@ declare module "node:buffer" {
              * If `totalLength` is not provided, it is calculated from the `Buffer` instances
              * in `list` by adding their lengths.
              *
-             * If `totalLength` is provided, it must be an unsigned integer. If the
+             * If `totalLength` is provided, it is coerced to an unsigned integer. If the
              * combined length of the `Buffer`s in `list` exceeds `totalLength`, the result is
              * truncated to `totalLength`.
              *
@@ -459,4 +459,10 @@ declare module "node:buffer" {
          */
         type AllowSharedBuffer = Buffer;
     }
+    /** @deprecated Use `Buffer.allocUnsafeSlow()` instead. */
+    var SlowBuffer: {
+        /** @deprecated Use `Buffer.allocUnsafeSlow()` instead. */
+        new(size: number): Buffer;
+        prototype: Buffer;
+    };
 }

package/server/node_modules/@types/node/ts5.6/globals.typedarray.d.ts

@@ -12,7 +12,6 @@ declare global {
             | Int32Array
             | BigUint64Array
             | BigInt64Array
-            | Float16Array
             | Float32Array
             | Float64Array;
         type ArrayBufferView = TypedArray | DataView;
@@ -26,7 +25,6 @@ declare global {
         type NonSharedInt32Array = Int32Array;
         type NonSharedBigUint64Array = BigUint64Array;
         type NonSharedBigInt64Array = BigInt64Array;
-        type NonSharedFloat16Array = Float16Array;
         type NonSharedFloat32Array = Float32Array;
         type NonSharedFloat64Array = Float64Array;
         type NonSharedDataView = DataView;

package/server/node_modules/@types/node/ts5.6/index.d.ts

@@ -22,37 +22,27 @@
  * IN THE SOFTWARE.
  */
 
-// NOTE: These definitions support Node.js and TypeScript 5.6.
+// NOTE: These definitions support Node.js and TypeScript 4.9 through 5.6.
 
-// Reference required TypeScript libraries:
+// Reference required TypeScript libs:
 /// <reference lib="es2020" />
-/// <reference lib="esnext.disposable" />
 
-// TypeScript library polyfills required for TypeScript <=5.6:
-/// <reference path="./compatibility/float16array.d.ts" />
+// TypeScript backwards-compatibility definitions:
+/// <reference path="../compatibility/index.d.ts" />
 
-// Definitions for Node.js modules specific to TypeScript <=5.6:
+// Definitions specific to TypeScript 4.9 through 5.6:
 /// <reference path="./globals.typedarray.d.ts" />
 /// <reference path="./buffer.buffer.d.ts" />
 
 // Definitions for Node.js modules that are not specific to any version of TypeScript:
 /// <reference path="../globals.d.ts" />
 /// <reference path="../web-globals/abortcontroller.d.ts" />
-/// <reference path="../web-globals/blob.d.ts" />
-/// <reference path="../web-globals/console.d.ts" />
-/// <reference path="../web-globals/crypto.d.ts" />
 /// <reference path="../web-globals/domexception.d.ts" />
-/// <reference path="../web-globals/encoding.d.ts" />
 /// <reference path="../web-globals/events.d.ts" />
 /// <reference path="../web-globals/fetch.d.ts" />
-/// <reference path="../web-globals/importmeta.d.ts" />
-/// <reference path="../web-globals/messaging.d.ts" />
 /// <reference path="../web-globals/navigator.d.ts" />
-/// <reference path="../web-globals/performance.d.ts" />
 /// <reference path="../web-globals/storage.d.ts" />
 /// <reference path="../web-globals/streams.d.ts" />
-/// <reference path="../web-globals/timers.d.ts" />
-/// <reference path="../web-globals/url.d.ts" />
 /// <reference path="../assert.d.ts" />
 /// <reference path="../assert/strict.d.ts" />
 /// <reference path="../async_hooks.d.ts" />
@@ -68,7 +58,6 @@
 /// <reference path="../dns/promises.d.ts" />
 /// <reference path="../domain.d.ts" />
 /// <reference path="../events.d.ts" />
-/// <reference path="../ffi.d.ts" />
 /// <reference path="../fs.d.ts" />
 /// <reference path="../fs/promises.d.ts" />
 /// <reference path="../http.d.ts" />
@@ -76,31 +65,25 @@
 /// <reference path="../https.d.ts" />
 /// <reference path="../inspector.d.ts" />
 /// <reference path="../inspector.generated.d.ts" />
-/// <reference path="../inspector/promises.d.ts" />
 /// <reference path="../module.d.ts" />
 /// <reference path="../net.d.ts" />
 /// <reference path="../os.d.ts" />
 /// <reference path="../path.d.ts" />
-/// <reference path="../path/posix.d.ts" />
-/// <reference path="../path/win32.d.ts" />
 /// <reference path="../perf_hooks.d.ts" />
 /// <reference path="../process.d.ts" />
 /// <reference path="../punycode.d.ts" />
 /// <reference path="../querystring.d.ts" />
-/// <reference path="../quic.d.ts" />
 /// <reference path="../readline.d.ts" />
 /// <reference path="../readline/promises.d.ts" />
 /// <reference path="../repl.d.ts" />
 /// <reference path="../sea.d.ts" />
 /// <reference path="../sqlite.d.ts" />
 /// <reference path="../stream.d.ts" />
-/// <reference path="../stream/consumers.d.ts" />
-/// <reference path="../stream/iter.d.ts" />
 /// <reference path="../stream/promises.d.ts" />
+/// <reference path="../stream/consumers.d.ts" />
 /// <reference path="../stream/web.d.ts" />
 /// <reference path="../string_decoder.d.ts" />
 /// <reference path="../test.d.ts" />
-/// <reference path="../test/reporters.d.ts" />
 /// <reference path="../timers.d.ts" />
 /// <reference path="../timers/promises.d.ts" />
 /// <reference path="../tls.d.ts" />
@@ -108,10 +91,8 @@
 /// <reference path="../tty.d.ts" />
 /// <reference path="../url.d.ts" />
 /// <reference path="../util.d.ts" />
-/// <reference path="../util/types.d.ts" />
 /// <reference path="../v8.d.ts" />
 /// <reference path="../vm.d.ts" />
 /// <reference path="../wasi.d.ts" />
 /// <reference path="../worker_threads.d.ts" />
 /// <reference path="../zlib.d.ts" />
-/// <reference path="../zlib/iter.d.ts" />

package/server/node_modules/@types/node/tty.d.ts

@@ -1,4 +1,29 @@
-declare module "node:tty" {
+/**
+ * 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
+ * import tty from 'node:tty';
+ * ```
+ *
+ * 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
+ * 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`:
+ *
+ * ```console
+ * $ node -p -e "Boolean(process.stdout.isTTY)"
+ * true
+ * $ node -p -e "Boolean(process.stdout.isTTY)" | cat
+ * false
+ * ```
+ *
+ * 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/v22.x/lib/tty.js)
+ */
+declare module "tty" {
     import * as net from "node:net";
     /**
      * The `tty.isatty()` method returns `true` if the given `fd` is associated with
@@ -50,9 +75,6 @@ declare module "node:tty" {
      *  1 - to the right from cursor
      */
     type Direction = -1 | 0 | 1;
-    interface WriteStreamEventMap extends net.SocketEventMap {
-        "resize": [];
-    }
     /**
      * 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.
@@ -60,6 +82,18 @@ declare module "node:tty" {
      */
     class WriteStream extends net.Socket {
         constructor(fd: number);
+        addListener(event: string, listener: (...args: any[]) => void): this;
+        addListener(event: "resize", listener: () => void): this;
+        emit(event: string | symbol, ...args: any[]): boolean;
+        emit(event: "resize"): boolean;
+        on(event: string, listener: (...args: any[]) => void): this;
+        on(event: "resize", listener: () => void): this;
+        once(event: string, listener: (...args: any[]) => void): this;
+        once(event: "resize", listener: () => void): this;
+        prependListener(event: string, listener: (...args: any[]) => void): this;
+        prependListener(event: "resize", listener: () => void): this;
+        prependOnceListener(event: string, listener: (...args: any[]) => void): this;
+        prependOnceListener(event: "resize", listener: () => void): this;
         /**
          * `writeStream.clearLine()` clears the current line of this `WriteStream` in a
          * direction identified by `dir`.
@@ -167,59 +201,8 @@ declare module "node:tty" {
          * @since v0.5.8
          */
         isTTY: boolean;
-        // #region InternalEventEmitter
-        addListener<E extends keyof WriteStreamEventMap>(
-            eventName: E,
-            listener: (...args: WriteStreamEventMap[E]) => void,
-        ): this;
-        addListener(eventName: string | symbol, listener: (...args: any[]) => void): this;
-        emit<E extends keyof WriteStreamEventMap>(eventName: E, ...args: WriteStreamEventMap[E]): boolean;
-        emit(eventName: string | symbol, ...args: any[]): boolean;
-        listenerCount<E extends keyof WriteStreamEventMap>(
-            eventName: E,
-            listener?: (...args: WriteStreamEventMap[E]) => void,
-        ): number;
-        listenerCount(eventName: string | symbol, listener?: (...args: any[]) => void): number;
-        listeners<E extends keyof WriteStreamEventMap>(eventName: E): ((...args: WriteStreamEventMap[E]) => void)[];
-        listeners(eventName: string | symbol): ((...args: any[]) => void)[];
-        off<E extends keyof WriteStreamEventMap>(
-            eventName: E,
-            listener: (...args: WriteStreamEventMap[E]) => void,
-        ): this;
-        off(eventName: string | symbol, listener: (...args: any[]) => void): this;
-        on<E extends keyof WriteStreamEventMap>(
-            eventName: E,
-            listener: (...args: WriteStreamEventMap[E]) => void,
-        ): this;
-        on(eventName: string | symbol, listener: (...args: any[]) => void): this;
-        once<E extends keyof WriteStreamEventMap>(
-            eventName: E,
-            listener: (...args: WriteStreamEventMap[E]) => void,
-        ): this;
-        once(eventName: string | symbol, listener: (...args: any[]) => void): this;
-        prependListener<E extends keyof WriteStreamEventMap>(
-            eventName: E,
-            listener: (...args: WriteStreamEventMap[E]) => void,
-        ): this;
-        prependListener(eventName: string | symbol, listener: (...args: any[]) => void): this;
-        prependOnceListener<E extends keyof WriteStreamEventMap>(
-            eventName: E,
-            listener: (...args: WriteStreamEventMap[E]) => void,
-        ): this;
-        prependOnceListener(eventName: string | symbol, listener: (...args: any[]) => void): this;
-        rawListeners<E extends keyof WriteStreamEventMap>(eventName: E): ((...args: WriteStreamEventMap[E]) => void)[];
-        rawListeners(eventName: string | symbol): ((...args: any[]) => void)[];
-        // eslint-disable-next-line @definitelytyped/no-unnecessary-generics
-        removeAllListeners<E extends keyof WriteStreamEventMap>(eventName?: E): this;
-        removeAllListeners(eventName?: string | symbol): this;
-        removeListener<E extends keyof WriteStreamEventMap>(
-            eventName: E,
-            listener: (...args: WriteStreamEventMap[E]) => void,
-        ): this;
-        removeListener(eventName: string | symbol, listener: (...args: any[]) => void): this;
-        // #endregion
     }
 }
-declare module "tty" {
-    export * from "node:tty";
+declare module "node:tty" {
+    export * from "tty";
 }