@wxt-dev/browser 0.0.331 → 0.0.332

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@wxt-dev/browser",
   "description": "Provides a cross-browser API for using extension APIs and types based on @types/chrome",
-  "version": "0.0.331",
+  "version": "0.0.332",
   "type": "module",
   "main": "src/index.mjs",
   "types": "src/index.d.ts",
@@ -19,7 +19,7 @@
     "src"
   ],
   "devDependencies": {
-    "@types/chrome": "0.0.331",
+    "@types/chrome": "0.0.332",
     "fs-extra": "^11.3.0",
     "nano-spawn": "^0.2.0",
     "tsx": "4.19.4",

package/src/gen/index.d.ts

@@ -8941,11 +8941,13 @@ export namespace Browser {
      * Use the `Browser.runtime` API to retrieve the service worker, return details about the manifest, and listen for and respond to events in the extension lifecycle. You can also use this API to convert the relative path of URLs to fully-qualified URLs.
      */
     export namespace runtime {
-        /** Populated with an error message if calling an API function fails; otherwise undefined. This is only defined within the scope of that function's callback. If an error is produced, but `runtime.lastError` is not accessed within the callback, a message is logged to the console listing the API function that produced the error. API functions that return promises do not set this property. */
-        export const lastError: {
+        export interface LastError {
             /** Details about the error which occurred.  */
             message?: string;
-        } | undefined;
+        }
+
+        /** Populated with an error message if calling an API function fails; otherwise undefined. This is only defined within the scope of that function's callback. If an error is produced, but `runtime.lastError` is not accessed within the callback, a message is logged to the console listing the API function that produced the error. API functions that return promises do not set this property. */
+        export const lastError: LastError | undefined;
 
         /** The ID of the extension/app. */
         export const id: string;
@@ -9173,6 +9175,11 @@ export namespace Browser {
             name: string;
         }
 
+        export interface UpdateAvailableDetails {
+            /** The version number of the available update. */
+            version: string;
+        }
+
         export interface UpdateCheckDetails {
             /** The version of the available update. */
             version: string;
@@ -9652,7 +9659,7 @@ export namespace Browser {
          */
         export function requestUpdateCheck(): Promise<RequestUpdateCheckResult>;
         export function requestUpdateCheck(
-            callback: (status: `${RequestUpdateCheckStatus}`, details?: { version: string }) => void,
+            callback: (status: `${RequestUpdateCheckStatus}`, details?: UpdateCheckDetails) => void,
         ): void;
 
         /** Restart the ChromeOS device when the app runs in kiosk mode. Otherwise, it's no-op. */
@@ -9771,7 +9778,7 @@ export namespace Browser {
         export const onRestartRequired: events.Event<(reason: `${OnRestartRequiredReason}`) => void>;
 
         /** Fired when an update is available, but isn't installed immediately because the app is currently running. If you do nothing, the update will be installed the next time the background page gets unloaded, if you want it to be installed sooner you can explicitly call Browser.runtime.reload(). If your extension is using a persistent background page, the background page of course never gets unloaded, so unless you call Browser.runtime.reload() manually in response to this event the update will not get installed until the next time Chrome itself restarts. If no handlers are listening for this event, and your extension has a persistent background page, it behaves as if Browser.runtime.reload() is called in response to this event. */
-        export const onUpdateAvailable: events.Event<(details: { version: string }) => void>;
+        export const onUpdateAvailable: events.Event<(details: UpdateAvailableDetails) => void>;
 
         /**
          * Fired when a Chrome update is available, but isn't installed immediately because a browser restart is required.