fix(messaging): Use callback syntax to avoid chrome 144 compatibility

issues

Author: aklinker1

packages/isolated-element/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@webext-core/isolated-element",
-  "version": "1.1.4",
+  "version": "2.0.0",
   "description": "Isolate content script UI's styles from the parent page. Supports all browsers (Chrome, Firefox, Safari)",
   "license": "MIT",
   "keywords": [

packages/messaging/src/extension.ts

@@ -79,9 +79,20 @@ export function defineExtensionMessaging<
       );
     },
     addRootListener(processMessage) {
-      const listener = (message: any, sender: Runtime.MessageSender) => {
-        if (typeof message === 'object') return processMessage({ ...message, sender });
-        else return processMessage(message);
+      const listener = (
+        message: any,
+        sender: Runtime.MessageSender,
+        sendResponse: (response?: any) => void,
+      ) => {
+        if (typeof message !== 'object') return;
+
+        const result = processMessage({ ...message, sender });
+        if (result instanceof Promise) {
+          result.then(sendResponse).catch(err => {
+            sendResponse({ __webextCoreError: err?.message ?? String(err) });
+          });
+          return true;
+        }
       };
 
       Browser.runtime.onMessage.addListener(listener);