@calo-design/cli 0.14.0 → 0.15.0

package/bin/cli.js

@@ -45,7 +45,16 @@ const PEERS = [
   // prototype (see mirror-push.js mirrorChromeSource). The shell binary provides
   // the native module (from build 8); prototypes ship JS only, and on older
   // binaries the SDK falls back to JS-only transport.
-  "@sentry/react-native"
+  "@sentry/react-native",
+  // Maps, voice notes and file/photo attachments (shell binary ships the native side
+  // from build 12). These were missing here, so a prototype that needed one hit
+  // "unable to resolve" and the natural fix — installing it into ~/.designchef/runtime
+  // by hand — produced a bundle whose native half didn't exist on the phone. That
+  // shipped caly-full: it opened to an expo-router error naming none of them.
+  "react-native-maps",
+  "expo-audio",
+  "expo-image-picker",
+  "expo-document-picker"
 ];
 // Install via explicit HTTPS git URLs. Auth is a short-lived GitHub token the Calo
 // broker mints after `calo-design login` — injected into git for the install

package/bin/mirror-push.js

@@ -40,7 +40,8 @@ const SHELL_MODULES = new Set([
   "expo", "expo-asset", "expo-camera", "expo-clipboard", "expo-constants", "expo-device",
   "expo-font", "expo-glass-effect", "expo-image", "expo-linking", "expo-router",
   "expo-splash-screen", "expo-status-bar", "expo-symbols", "expo-system-ui", "expo-updates",
-  "expo-video", "expo-web-browser", "phosphor-react-native", "react", "react-dom",
+  "expo-video", "expo-web-browser", "expo-audio", "expo-document-picker", "expo-image-picker",
+  "expo-file-system", "react-native-maps", "phosphor-react-native", "react", "react-dom",
   "react-native", "react-native-gesture-handler", "react-native-qrcode-svg",
   "react-native-reanimated", "react-native-safe-area-context", "react-native-screens",
   "react-native-svg", "react-native-web", "react-native-worklets",
@@ -172,10 +173,27 @@ function validateDeps(pkg) {
   }
   const runtimeDeps = new Set(Object.keys(JSON.parse(fs.readFileSync(runtimePkgPath, "utf8")).dependencies || {}));
   const extras = Object.keys(pkg.dependencies || {}).filter((d) => !d.startsWith("@calo/") && !runtimeDeps.has(d));
-  if (extras.length) {
-    warn(`these deps aren't in the shared runtime, so the Mirror binary can't provide them:\n    ${extras.join(", ")}`);
-    warn("the prototype may crash on load in Mirror. Keep prototypes to the shared-runtime deps, or ask for a runtime bump.");
+  if (!extras.length) return;
+
+  // A dep the runtime lacks normally can't even bundle — but "unable to resolve X" is
+  // reasonably fixed by installing X into ~/.designchef/runtime by hand, and then the
+  // push succeeds and the PHONE has no native side for it. That is how caly-full went
+  // out: expo-audio, expo-image-picker, expo-document-picker and react-native-maps were
+  // all declared here, all absent from the runtime, and the prototype died on open with
+  // an expo-router error naming none of them. So: anything the shell binary can't serve
+  // is a hard stop, not a warning nobody reads.
+  const unusable = extras.filter((d) => !SHELL_MODULES.has(d));
+  if (unusable.length) {
+    throw new Error(
+      `these dependencies aren't in the shared runtime AND aren't in the Mirror shell binary:\n` +
+      `    ${unusable.join(", ")}\n` +
+      `  Even if the bundle builds (e.g. they were installed into the runtime by hand), the phone\n` +
+      `  has no native code for them: the import throws on open and the prototype shows an\n` +
+      `  unrelated expo-router error. Drop them, or ask for a runtime + shell bump that carries them.`
+    );
   }
+  warn(`these deps aren't in the shared runtime, so the bundle can only build if they're installed there:\n    ${extras.join(", ")}`);
+  warn("the Mirror binary does carry their native side — but keep prototypes to the shared-runtime deps where you can.");
 }
 
 function writeJSON(p, obj) {
@@ -333,7 +351,7 @@ function isNativePackage(name) {
   try {
     return fs.readdirSync(dir).some((f) => f.endsWith(".podspec"));
   } catch {
-    return false; // not installed in the runtime — validateDeps already covered that
+    return false; // not in the runtime — validateDeps owns that case
   }
 }
 
@@ -1095,4 +1113,4 @@ async function cmdPush(args) {
   }
 }
 
-module.exports = { cmdPush, _stageSkipDirs: STAGE_SKIP_DIRS, _s3Put: s3Put, _upsertRegistry: upsertRegistry, _publicBase: PUBLIC_BASE, _extractEasGroup: extractEasGroup, _versionBranchOf: versionBranchOf, _stagedImports: stagedImports, _preflightNativeModules: preflightNativeModules, _shellModules: SHELL_MODULES };
+module.exports = { cmdPush, _validateDeps: validateDeps, _stageSkipDirs: STAGE_SKIP_DIRS, _s3Put: s3Put, _upsertRegistry: upsertRegistry, _publicBase: PUBLIC_BASE, _extractEasGroup: extractEasGroup, _versionBranchOf: versionBranchOf, _stagedImports: stagedImports, _preflightNativeModules: preflightNativeModules, _shellModules: SHELL_MODULES };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@calo-design/cli",
-  "version": "0.14.0",
+  "version": "0.15.0",
   "description": "One-line setup for Calo design tooling: logs in with your Calo email and installs the calo-design skill + design-system packages. No GitHub account needed.",
   "bin": {
     "calo-design": "bin/cli.js"