@everystack/cli 0.2.3 → 0.2.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@everystack/cli",
-  "version": "0.2.3",
+  "version": "0.2.5",
   "description": "CLI and OTA updates for Expo apps on everystack",
   "license": "AGPL-3.0-only",
   "publishConfig": {

package/src/cli/commands/update.ts

@@ -16,6 +16,7 @@ export interface UpdateFlags {
   branch?: string;
   message?: string;
   platform?: string;
+  environment?: string;
   export?: string;
 }
 
@@ -26,12 +27,13 @@ export async function updateCommand(flags: UpdateFlags & Record<string, string>)
   // (e.g. OUTBOUND_HOST=localhost → LAN IP) to leak into the manifest.
   process.env.EVERYSTACK_UPDATE = '1';
 
-  // Propagate --stage to ENVIRONMENT before app.config.js evaluation.
-  // Without this, the manifest snapshots whatever the local shell has
-  // (often unset → 'development'), baking wrong API URLs and feature
-  // flags into the OTA update.  Only set if not already supplied.
-  if (flags.stage) {
-    process.env.ENVIRONMENT ||= flags.stage;
+  // Set ENVIRONMENT before app.config.js evaluation so the manifest
+  // snapshots the correct API URLs and feature flags for the target.
+  // --environment is explicit; --stage is NOT used as a fallback because
+  // SST stage names (dev, prod) don't match EAS profile names
+  // (development, production) and conflating them causes config failures.
+  if (flags.environment) {
+    process.env.ENVIRONMENT ||= flags.environment;
   }
 
   // When --stage is provided, resolve deployed config early so HOST_URL
@@ -412,8 +414,17 @@ async function loadAppConfig(): Promise<any> {
       // Handle Expo's function export pattern: export default () => ({ ... })
       if (typeof resolved === 'function') resolved = resolved();
       return resolved.expo || resolved;
-    } catch {
-      throw new Error('Could not find app.json or app.config.js');
+    } catch (e) {
+      const configPath = path.resolve('app.config.js');
+      try {
+        await fs.access(configPath);
+        // File exists but failed to import — surface the real error
+        throw new Error(`Failed to load app.config.js: ${e instanceof Error ? e.message : e}`);
+      } catch (accessErr) {
+        if (accessErr instanceof Error && accessErr.message.startsWith('Failed to load'))
+          throw accessErr;
+        throw new Error('Could not find app.json or app.config.js');
+      }
     }
   }
 }

package/src/cli/index.ts

@@ -150,8 +150,8 @@ function printHelp() {
 everystack - CLI for Expo apps on everystack
 
 Usage:
-  everystack update            --branch <name> --message <msg> [--platform ios|android|web|all] [--stage <name>] [--skip-export]
-  everystack update            --channel <name> --message <msg> [--platform ios|android|web|all] [--stage <name>] [--skip-export]
+  everystack update            --branch <name> --message <msg> [--platform ios|android|web|all] [--stage <name>] [--environment <name>] [--skip-export]
+  everystack update            --channel <name> --message <msg> [--platform ios|android|web|all] [--stage <name>] [--environment <name>] [--skip-export]
   everystack db:migrate        [--stage <name>]  Run database migrations on deployed Lambda
   everystack db:seed           [--stage <name>]  Seed database on deployed Lambda (dev only)
   everystack db:reset          [--stage <name>]  Drop all schemas + re-run migrations (dev only)
@@ -183,6 +183,9 @@ Stage resolution:
 
   Without --stage, reads .sst/outputs.json (written by the last \`sst deploy\`).
 
+  --environment <name>  Set ENVIRONMENT for app.config.js evaluation (e.g. development, staging, production).
+                        Use this when your SST stage name differs from your EAS build profile name.
+
 Auth:
   All commands use AWS IAM credentials (default credential chain).
   Mobile publishes also accept EVERYSTACK_TOKEN env var.