chrome-types 0.1.278 → 0.1.279

package/_all.d.ts

@@ -14,8 +14,8 @@
  * limitations under the License.
  */
 
-// Generated on Mon Apr 08 2024 22:30:29 GMT+0000 (Coordinated Universal Time)
-// Built at 79e17af4688d09d94be946412f9d874a7ce5b4cd
+// Generated on Wed Apr 10 2024 22:30:10 GMT+0000 (Coordinated Universal Time)
+// Built at 606475c6ec831eafa70978b96731cef50c784d53
 
 // Includes all types, including MV2 + Platform Apps APIs.
 
@@ -7410,7 +7410,7 @@ declare namespace chrome {
   namespace _debugger {
 
     /**
-     * Debuggee identifier. Either tabId or extensionId must be specified
+     * Debuggee identifier. Either tabId, extensionId or targetId must be specified
      */
     export interface Debuggee {
 
@@ -7430,6 +7430,34 @@ declare namespace chrome {
       targetId?: string;
     }
 
+    /**
+     * Debugger session identifier. One of tabId, extensionId or targetId must be specified. Additionally, an optional sessionId can be provided. If sessionId is specified for arguments sent from {@link onEvent}, it means the event is coming from a child protocol session within the root debuggee session. If sessionId is specified when passed to {@link sendCommand}, it targets a child protocol session within the root debuggee session.
+     *
+     * @since Pending
+     */
+    export interface DebuggerSession {
+
+      /**
+       * The id of the tab which you intend to debug.
+       */
+      tabId?: number;
+
+      /**
+       * The id of the extension which you intend to debug. Attaching to an extension background page is only possible when the `--silent-debugger-extension-api` command-line switch is used.
+       */
+      extensionId?: string;
+
+      /**
+       * The opaque id of the debug target.
+       */
+      targetId?: string;
+
+      /**
+       * The opaque id of the Chrome DevTools Protocol session. Identifies a child session within the root session identified by tabId, extensionId or targetId.
+       */
+      sessionId?: string;
+    }
+
     /**
      * Target type.
      *
@@ -7494,7 +7522,7 @@ declare namespace chrome {
      * Fired whenever debugging target issues instrumentation event.
      */
     export const onEvent: events.Event<(
-      source: Debuggee,
+      source: DebuggerSession,
       method: string,
       params?: {[name: string]: any},
     ) => void>;
@@ -7571,7 +7599,7 @@ declare namespace chrome {
      */
     export function sendCommand(
 
-      target: Debuggee,
+      target: DebuggerSession,
 
       method: string,
 
@@ -7588,7 +7616,7 @@ declare namespace chrome {
      */
     export function sendCommand(
 
-      target: Debuggee,
+      target: DebuggerSession,
 
       method: string,
 

package/index.d.ts

@@ -14,8 +14,8 @@
  * limitations under the License.
  */
 
-// Generated on Mon Apr 08 2024 22:30:24 GMT+0000 (Coordinated Universal Time)
-// Built at 79e17af4688d09d94be946412f9d874a7ce5b4cd
+// Generated on Wed Apr 10 2024 22:30:05 GMT+0000 (Coordinated Universal Time)
+// Built at 606475c6ec831eafa70978b96731cef50c784d53
 
 // Includes MV3+ APIs only.
 
@@ -4156,7 +4156,7 @@ declare namespace chrome {
   namespace _debugger {
 
     /**
-     * Debuggee identifier. Either tabId or extensionId must be specified
+     * Debuggee identifier. Either tabId, extensionId or targetId must be specified
      */
     export interface Debuggee {
 
@@ -4176,6 +4176,34 @@ declare namespace chrome {
       targetId?: string;
     }
 
+    /**
+     * Debugger session identifier. One of tabId, extensionId or targetId must be specified. Additionally, an optional sessionId can be provided. If sessionId is specified for arguments sent from {@link onEvent}, it means the event is coming from a child protocol session within the root debuggee session. If sessionId is specified when passed to {@link sendCommand}, it targets a child protocol session within the root debuggee session.
+     *
+     * @since Pending
+     */
+    export interface DebuggerSession {
+
+      /**
+       * The id of the tab which you intend to debug.
+       */
+      tabId?: number;
+
+      /**
+       * The id of the extension which you intend to debug. Attaching to an extension background page is only possible when the `--silent-debugger-extension-api` command-line switch is used.
+       */
+      extensionId?: string;
+
+      /**
+       * The opaque id of the debug target.
+       */
+      targetId?: string;
+
+      /**
+       * The opaque id of the Chrome DevTools Protocol session. Identifies a child session within the root session identified by tabId, extensionId or targetId.
+       */
+      sessionId?: string;
+    }
+
     /**
      * Target type.
      *
@@ -4240,7 +4268,7 @@ declare namespace chrome {
      * Fired whenever debugging target issues instrumentation event.
      */
     export const onEvent: events.Event<(
-      source: Debuggee,
+      source: DebuggerSession,
       method: string,
       params?: {[name: string]: any},
     ) => void>;
@@ -4317,7 +4345,7 @@ declare namespace chrome {
      */
     export function sendCommand(
 
-      target: Debuggee,
+      target: DebuggerSession,
 
       method: string,
 
@@ -4334,7 +4362,7 @@ declare namespace chrome {
      */
     export function sendCommand(
 
-      target: Debuggee,
+      target: DebuggerSession,
 
       method: string,
 

package/package.json

@@ -5,7 +5,7 @@
   "type": "module",
   "name": "chrome-types",
   "config": {
-    "build-hash": "b06b960a47fbaa60"
+    "build-hash": "a66a589486597e54"
   },
   "repository": {
     "type": "git",
@@ -16,5 +16,5 @@
     "url": "https://github.com/GoogleChrome/chrome-types/issues"
   },
   "homepage": "https://github.com/GoogleChrome/chrome-types",
-  "version": "0.1.278"
+  "version": "0.1.279"
 }