@myop/sdk 0.4.0-beta.3 → 0.4.0-beta.5

package/dist/module/host/loaders/HTMLComponentLoader.d.ts

@@ -7,7 +7,25 @@ import { MyopIframeComponent } from "../components/myopIframeComponent.ts";
 export declare class HTMLComponentLoader extends BaseMyopLoader {
     type: "HTMLLoader";
     /**
-     * Detect if HTML is a Myop Web Component (starts with marker comment)
+     * Detect if HTML is a Myop Web Component.
+     *
+     * THE MARKER COMMENT ALONE IS NOT A SAFE SIGNAL, BECAUSE MINIFIERS DELETE COMMENTS.
+     *
+     * This used to be `startsWith(MYOP_WEB_COMPONENT_MARKER)` and nothing else. The
+     * delivery lane minifies with `removeComments: true` (myop-server derive.ts MIN_CFG),
+     * so the stored `min` artifact of every v2 web component loses its leading
+     * `<!-- myop-web-component -->`. Detection then returned false, the component fell
+     * back to plain iframe rendering, and the whole authored document was shown --
+     * including the v2 authoring wrapper, so Pic-Time's production dashboard displayed the
+     * preview chrome ("Web Component v2", a tag-name badge reading `loading...`, SIZE /
+     * OVERFLOW / BG controls) instead of their component. Reported 2026-10-18; the served
+     * HTML measured 328,071 bytes against 951,130 at origin, with zero `<!--` left in it.
+     *
+     * The script id is the signal that survives, and it is the one `extractWebComponentScript`
+     * already depends on: if that element is present, extraction works, so detection
+     * should agree. Checked with a regex rather than DOMParser -- this runs for every
+     * HTML component, and parsing a 300 KB document to answer a yes/no question is not
+     * worth it.
      */
     private isMyopWebComponent;
     /**