@decocms/blocks-admin 7.16.2 → 7.16.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@decocms/blocks-admin",
-  "version": "7.16.2",
+  "version": "7.16.4",
   "type": "module",
   "description": "Deco admin protocol: /live/_meta, /.decofile, /deco/invoke, /deco/render, plus admin-facing site setup and commerce-app auto-configuration",
   "repository": {
@@ -25,7 +25,7 @@
     "lint:unused": "knip"
   },
   "dependencies": {
-    "@decocms/blocks": "7.16.2"
+    "@decocms/blocks": "7.16.4"
   },
   "peerDependencies": {
     "react": "^19.0.0",

package/src/apps/autoconfig.ts

@@ -95,8 +95,21 @@ async function configureAllApps(
         handlers: mod.handlers,
       };
       apps.push(withHandlers);
-    } catch {
-      // App module missing, configure threw, or block was malformed — skip.
+    } catch (err) {
+      // The app is present in the decofile (block matched) but couldn't be
+      // configured — module load failed, configure() threw, or the block was
+      // malformed. We still skip it so one broken app can't take down setup,
+      // but we must NOT swallow silently: a failure here means the app's
+      // loaders/actions never register, so its sections resolve to null at
+      // runtime with no other signal. Common cause: the registry entry's
+      // `module: () => import("...")` dynamic import failing to resolve in a
+      // production bundle (works under `vite dev`) — the fix is a static module
+      // reference in the app's registry entry.
+      console.error(
+        `[autoconfigApps] failed to configure app "${entry.blockKey}" — its ` +
+          `loaders/actions will NOT be registered (matching sections resolve to null):`,
+        err,
+      );
     }
   }