@jay-framework/webmcp-plugin 0.12.0 → 0.14.0

package/dist/index.client.js

@@ -311,7 +311,7 @@ function interactionKey(automation) {
   ).join("|");
 }
 const init = makeJayInit().withClient(() => {
-  setTimeout(() => {
+  const setup = () => {
     const automation = window.__jay?.automation;
     if (automation) {
       const cleanup = setupWebMCP(automation);
@@ -319,7 +319,12 @@ const init = makeJayInit().withClient(() => {
     } else {
       console.warn("[WebMCP] window.__jay.automation not available — skipping");
     }
-  }, 0);
+  };
+  if (window.__jay?.automation) {
+    setup();
+  } else {
+    window.addEventListener("jay:automation-ready", setup, { once: true });
+  }
 });
 export {
   init,

package/dist/index.d.ts

@@ -4,17 +4,10 @@ import { AutomationAPI } from '@jay-framework/runtime-automation';
 /**
  * WebMCP plugin init — client-only.
  *
- * Uses setTimeout(0) to defer setup until after the current task completes:
- * 1. All plugin client inits (each `await`ed, creating microtasks)
- * 2. Page component is created and mounted
- * 3. wrapWithAutomation() is called
- * 4. window.__jay.automation is set
- *
- * Why setTimeout and not queueMicrotask:
- * Plugin inits are `await`ed in the generated script. `await undefined` yields
- * to the microtask queue, so a queueMicrotask callback runs BEFORE the rest of
- * the script (component creation, automation setup). setTimeout(0) schedules on
- * the macrotask queue, which runs after all synchronous code and microtasks.
+ * Listens for the 'jay:automation-ready' event dispatched by the generated
+ * client script after window.__jay.automation is set. This avoids the race
+ * condition where a setTimeout(0) could fire during another plugin's async
+ * init, before automation is available.
  */
 declare const init: _jay_framework_fullstack_component.JayInit<void>;
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jay-framework/webmcp-plugin",
-  "version": "0.12.0",
+  "version": "0.14.0",
   "type": "module",
   "license": "Apache-2.0",
   "description": "WebMCP plugin for jay-stack — automatically exposes page interactions as WebMCP tools, resources, and prompts",
@@ -28,12 +28,12 @@
     "test:watch": "vitest"
   },
   "dependencies": {
-    "@jay-framework/fullstack-component": "^0.12.0",
-    "@jay-framework/runtime-automation": "^0.12.0"
+    "@jay-framework/fullstack-component": "^0.14.0",
+    "@jay-framework/runtime-automation": "^0.14.0"
   },
   "devDependencies": {
-    "@jay-framework/compiler-jay-stack": "^0.12.0",
-    "@jay-framework/dev-environment": "^0.12.0",
+    "@jay-framework/compiler-jay-stack": "^0.14.0",
+    "@jay-framework/dev-environment": "^0.14.0",
     "@types/node": "^20.11.5",
     "rimraf": "^5.0.5",
     "tsup": "^8.0.1",