@elytracms/next 0.0.97 → 0.0.98

package/dist/index.d.ts

@@ -1415,7 +1415,16 @@ interface NextImageOptions {
  *
  * Which entry fills the role is decided by core's one registration rule (the first
  * valid claimant — `ComponentRegistry.roleComponent('image')`), so the swap can
- * never land on a different entry than the one the registry resolves. Use it on
+ * never land on a different entry than the one the registry resolves.
+ *
+ * It registers the list BEFORE `createElytraHost` resolves the entry through the config
+ * gate, so it must not be the first place a broken list is read (EC-678): the
+ * registration never throws — a malformed manifest is a located finding, and the gate
+ * reads the same registration — so a broken list comes back from here unchanged and the
+ * host's boot throws the gate's LOCATED error (`invalid-config-shape at
+ * components.N.manifest.props.p: …`), the same one `elytra doctor` `config-valid` and the
+ * studio report. (Measured on `6310b7b4`: a prop that was not a field-def threw here,
+ * unlocated, before the gate ran.) Use it on
  * the DELIVERY side only (the studio's canvas runs on Vite, where `next/image`
  * does not exist) — the scaffold's host seam file does it in one line:
  *

package/dist/index.js

@@ -1074,7 +1074,9 @@ function withNextImage(components, options = {}) {
   const image = registerComponents(list).registry.roleComponent("image");
   if (!image) return list;
   const implementation = createNextImage(options);
-  return list.map((entry) => entry.manifest === image ? { manifest: entry.manifest, implementation } : entry);
+  return list.map(
+    (entry) => entry?.manifest === image ? { manifest: entry.manifest, implementation } : entry
+  );
 }
 function elytraHostImage(options = {}) {
   return ({ asset, alt, className, priority, sizes, loading }) => /* @__PURE__ */ jsx(