@trackunit/react-vite-test-setup 0.0.7 → 0.0.8

package/index.cjs.js

@@ -661,6 +661,78 @@ const setupTranslations = () => {
     }));
 };
 
+const TARGET_ORIGIN_WILDCARD = "*";
+let postMessagePolyfillInstalled = false;
+const patchedPostMessageWindows = new WeakSet();
+/**
+ * Wrap a window's `postMessage` so it accepts both the legacy
+ * `postMessage(message, targetOrigin)` and the modern
+ * `postMessage(message, { targetOrigin, transfer })` signatures, forwarding
+ * either to the legacy two-arg form that jsdom understands. Idempotent per
+ * window instance.
+ */
+const patchWindowPostMessage = (target) => {
+    if (patchedPostMessageWindows.has(target)) {
+        return;
+    }
+    const originalPostMessage = target.postMessage.bind(target);
+    const wrapped = (message, optionsOrTargetOrigin) => {
+        let targetOrigin = TARGET_ORIGIN_WILDCARD;
+        if (typeof optionsOrTargetOrigin === "string") {
+            targetOrigin = optionsOrTargetOrigin;
+        }
+        else if (typeof optionsOrTargetOrigin === "object" &&
+            optionsOrTargetOrigin !== null &&
+            "targetOrigin" in optionsOrTargetOrigin &&
+            typeof optionsOrTargetOrigin.targetOrigin === "string") {
+            targetOrigin = optionsOrTargetOrigin.targetOrigin;
+        }
+        originalPostMessage(message, targetOrigin);
+    };
+    Object.defineProperty(target, "postMessage", { value: wrapped, writable: true, configurable: true });
+    patchedPostMessageWindows.add(target);
+};
+/**
+ * Polyfill jsdom's `Window.postMessage` so it accepts the modern
+ * `postMessage(message, { targetOrigin, transfer })` options-object form in
+ * addition to the legacy `postMessage(message, targetOrigin)` form.
+ *
+ * Penpal v7's `WindowMessenger.sendMessage` uses the options-object form
+ * (part of the WHATWG HTML spec, supported by real browsers and happy-dom),
+ * but jsdom 26 still only implements the legacy two-arg form and stringifies
+ * the options object into the target-origin slot. Any component test that
+ * either initialises the iris-app-runtime `HostConnector` singleton (via
+ * `ThemeCssProviderIrisApp` → `getThemeCssProperties`) or mounts a
+ * `WidgetExtensionFrame` / `IrisAppIframe` (via `usePenpalIframe`'s
+ * `WindowMessenger({ remoteWindow: iframe.contentWindow })`) then blows up
+ * with `Invalid target origin '[object Object]'`.
+ *
+ * jsdom installs `postMessage` as an own property on every window (including
+ * iframe `contentWindow`s), so a plain `Window.prototype` patch doesn't
+ * cover iframes. Hook the prototype's `contentWindow` getter to lazy-patch
+ * iframe windows on first access. Idempotent.
+ */
+const installPostMessagePolyfill = () => {
+    if (postMessagePolyfillInstalled) {
+        return;
+    }
+    patchWindowPostMessage(window);
+    const iframeDescriptor = Object.getOwnPropertyDescriptor(HTMLIFrameElement.prototype, "contentWindow");
+    if (iframeDescriptor?.get && iframeDescriptor.configurable) {
+        const originalGetter = iframeDescriptor.get;
+        Object.defineProperty(HTMLIFrameElement.prototype, "contentWindow", {
+            configurable: true,
+            get: function getContentWindow() {
+                const contentWindow = originalGetter.call(this);
+                if (contentWindow !== null) {
+                    patchWindowPostMessage(contentWindow);
+                }
+                return contentWindow;
+            },
+        });
+    }
+    postMessagePolyfillInstalled = true;
+};
 /**
  * Flushes all promises in the queue.
  * This is useful when testing async code.
@@ -900,6 +972,7 @@ const setupReactTestingLibrary = () => {
     setupMatchMediaMock();
     setupResizeObserver();
     setupIntersectionObserver();
+    installPostMessagePolyfill();
 };
 
 /**

package/index.esm.js

@@ -640,6 +640,78 @@ const setupTranslations = () => {
     }));
 };
 
+const TARGET_ORIGIN_WILDCARD = "*";
+let postMessagePolyfillInstalled = false;
+const patchedPostMessageWindows = new WeakSet();
+/**
+ * Wrap a window's `postMessage` so it accepts both the legacy
+ * `postMessage(message, targetOrigin)` and the modern
+ * `postMessage(message, { targetOrigin, transfer })` signatures, forwarding
+ * either to the legacy two-arg form that jsdom understands. Idempotent per
+ * window instance.
+ */
+const patchWindowPostMessage = (target) => {
+    if (patchedPostMessageWindows.has(target)) {
+        return;
+    }
+    const originalPostMessage = target.postMessage.bind(target);
+    const wrapped = (message, optionsOrTargetOrigin) => {
+        let targetOrigin = TARGET_ORIGIN_WILDCARD;
+        if (typeof optionsOrTargetOrigin === "string") {
+            targetOrigin = optionsOrTargetOrigin;
+        }
+        else if (typeof optionsOrTargetOrigin === "object" &&
+            optionsOrTargetOrigin !== null &&
+            "targetOrigin" in optionsOrTargetOrigin &&
+            typeof optionsOrTargetOrigin.targetOrigin === "string") {
+            targetOrigin = optionsOrTargetOrigin.targetOrigin;
+        }
+        originalPostMessage(message, targetOrigin);
+    };
+    Object.defineProperty(target, "postMessage", { value: wrapped, writable: true, configurable: true });
+    patchedPostMessageWindows.add(target);
+};
+/**
+ * Polyfill jsdom's `Window.postMessage` so it accepts the modern
+ * `postMessage(message, { targetOrigin, transfer })` options-object form in
+ * addition to the legacy `postMessage(message, targetOrigin)` form.
+ *
+ * Penpal v7's `WindowMessenger.sendMessage` uses the options-object form
+ * (part of the WHATWG HTML spec, supported by real browsers and happy-dom),
+ * but jsdom 26 still only implements the legacy two-arg form and stringifies
+ * the options object into the target-origin slot. Any component test that
+ * either initialises the iris-app-runtime `HostConnector` singleton (via
+ * `ThemeCssProviderIrisApp` → `getThemeCssProperties`) or mounts a
+ * `WidgetExtensionFrame` / `IrisAppIframe` (via `usePenpalIframe`'s
+ * `WindowMessenger({ remoteWindow: iframe.contentWindow })`) then blows up
+ * with `Invalid target origin '[object Object]'`.
+ *
+ * jsdom installs `postMessage` as an own property on every window (including
+ * iframe `contentWindow`s), so a plain `Window.prototype` patch doesn't
+ * cover iframes. Hook the prototype's `contentWindow` getter to lazy-patch
+ * iframe windows on first access. Idempotent.
+ */
+const installPostMessagePolyfill = () => {
+    if (postMessagePolyfillInstalled) {
+        return;
+    }
+    patchWindowPostMessage(window);
+    const iframeDescriptor = Object.getOwnPropertyDescriptor(HTMLIFrameElement.prototype, "contentWindow");
+    if (iframeDescriptor?.get && iframeDescriptor.configurable) {
+        const originalGetter = iframeDescriptor.get;
+        Object.defineProperty(HTMLIFrameElement.prototype, "contentWindow", {
+            configurable: true,
+            get: function getContentWindow() {
+                const contentWindow = originalGetter.call(this);
+                if (contentWindow !== null) {
+                    patchWindowPostMessage(contentWindow);
+                }
+                return contentWindow;
+            },
+        });
+    }
+    postMessagePolyfillInstalled = true;
+};
 /**
  * Flushes all promises in the queue.
  * This is useful when testing async code.
@@ -879,6 +951,7 @@ const setupReactTestingLibrary = () => {
     setupMatchMediaMock();
     setupResizeObserver();
     setupIntersectionObserver();
+    installPostMessagePolyfill();
 };
 
 /**

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@trackunit/react-vite-test-setup",
   "description": "Test setup utilities for React applications",
-  "version": "0.0.7",
+  "version": "0.0.8",
   "repository": "https://github.com/Trackunit/manager",
   "license": "SEE LICENSE IN LICENSE.txt",
   "engines": {