@jxsuite/runtime 1.3.0 → 1.3.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jxsuite/runtime",
-  "version": "1.3.0",
+  "version": "1.3.2",
   "description": "JSON-native reactive web component runtime",
   "license": "MIT",
   "repository": {
@@ -30,10 +30,10 @@
     "upgrade": "bunx npm-check-updates -u && bun install"
   },
   "dependencies": {
-    "@jxsuite/schema": "^1.3.0",
+    "@jxsuite/schema": "^1.5.0",
     "@vue/reactivity": "3.5.40"
   },
   "devDependencies": {
-    "@happy-dom/global-registrator": "^20.11.0"
+    "@happy-dom/global-registrator": "^20.11.1"
   }
 }

package/src/runtime.ts

@@ -170,6 +170,25 @@ export function setSkipServerFunctions(v: boolean) {
   _serverFnConfig.skip = v;
 }
 
+/** @type {{ skip: boolean }} */
+const _autoRequestConfig = { skip: false };
+/**
+ * Set to true to suppress AUTOMATIC `$prototype: "Request"` fetches — the sibling of
+ * {@link setSkipServerFunctions}, and used by Studio for the same reason.
+ *
+ * `buildScope` re-resolves every `state` entry on each full canvas render, so an auto-request
+ * re-issued its HTTP call every time the canvas rebuilt. In edit/design mode that meant authoring
+ * actions — a signal edit, or pressing Enter inside component-wrapped content, both of which force
+ * a full render — fired network requests. Live data belongs to preview and to the deployed site.
+ *
+ * Only non-`manual` requests are gated: a `manual` one fires from an event handler, and edit mode
+ * strips handlers before rendering. The returned ref is unchanged either way — it simply stays at
+ * its initial `null`, which is the same state bindings observe before any fetch resolves.
+ */
+export function setSkipAutoRequests(v: boolean) {
+  _autoRequestConfig.skip = v;
+}
+
 // ─── Dev-proxy auth token (Studio cross-origin canvas) ────────────────────────
 // The Studio canvas iframe is served from a token-gated loopback origin (createProjectServer): its
 // POST /__jx_resolve__ + /__jx_server__ routes 403 without ?token=<rpcToken>. The iframe boot reads
@@ -773,6 +792,17 @@ export function renderNode(
   }
 
   if (def.$props) {
+    // A hyphenated tag carrying $props is a component instance whose definition has not finished
+    // Registering yet (async defineElement — e.g. the Studio desktop canvas, where the component
+    // Fetch can land after this node renders). Render via the property-first path anyway: it sets
+    // The instance props as JS properties on the bare element, which the eventual upgrade's
+    // ConnectedCallback reads back off `this` (see the def.state merge below), so the instance's
+    // Props win. The old branch stripped the props here, so a late upgrade painted the component's
+    // State DEFAULTS instead ("0"/"DESCRIPTION" for every instance). A non-custom tag can never
+    // Upgrade, so it keeps the historical mergeProps-into-scope behavior.
+    if (tagName.includes("-")) {
+      return renderCustomElementWithProps(def, localState, options, path);
+    }
     const { $props: _$props, ...rest } = def;
     return renderNode(rest, mergeProps(def, localState), options);
   }
@@ -1312,7 +1342,7 @@ export async function resolvePrototype(
       const debounceMs = def.debounce ?? 0;
       let debounceTimer: ReturnType<typeof setTimeout> | null = null;
 
-      if (!def.manual) {
+      if (!def.manual && !_autoRequestConfig.skip) {
         effect(() => {
           let url: string | undefined;
           if (isTemplateString(def.url)) {