@overscore/cli 0.13.11 → 0.13.12

package/dist/index.js

@@ -431,6 +431,9 @@ function extractZip(zipBuffer, targetDir) {
 }
 // ── Commands ────────────────────────────────────────────────────────
 async function deploy() {
+    // Refuse to deploy to the wrong hub (e.g. a staging dashboard to prod because
+    // OVERSCORE_HUB_URL wasn't set). Runs before loadEnv so it fails fast.
+    assertHubMatchesEnv();
     const { apiUrl, apiKey, dashboardSlug } = await loadEnv();
     // Parse --message flag
     const msgIndex = process.argv.indexOf("--message");
@@ -1177,6 +1180,46 @@ const HUB_HOST = (() => {
         return "overscore.dev";
     }
 })();
+/**
+ * Fail fast on a hub mismatch. A dashboard's .env names the hub it belongs to
+ * (VITE_OVERSCORE_API_URL), but credentialed CLI ops (key minting, deploy
+ * upload) target HUB_URL — which only repoints at staging when the operator
+ * sets OVERSCORE_HUB_URL. When the .env names a different host than HUB_URL, the
+ * CLI silently falls back to prod (safeApiUrl, audit L6) and mints a key /
+ * deploys to the WRONG hub, surfacing later as a baffling "Invalid API key" in
+ * the browser. We do NOT trust the .env host for anything credentialed — we
+ * just detect the mismatch and tell the user which env var to set. Localhost
+ * dashboards are dev-only and always fine.
+ */
+function assertHubMatchesEnv() {
+    const envPath = path.resolve(process.cwd(), ".env");
+    if (!fs.existsSync(envPath))
+        return;
+    const envApiUrl = parseEnv(fs.readFileSync(envPath, "utf-8")).VITE_OVERSCORE_API_URL;
+    if (!envApiUrl)
+        return;
+    let envHost;
+    try {
+        envHost = new URL(envApiUrl).hostname;
+    }
+    catch {
+        return;
+    }
+    if (envHost === "localhost" || envHost === "127.0.0.1" || envHost === HUB_HOST)
+        return;
+    const envBase = envApiUrl.replace(/\/api\/?$/, "").replace(/\/+$/, "");
+    console.error(`
+  Error: this dashboard targets ${envHost}, but the CLI is pointed at ${HUB_HOST}.
+
+  Credentialed commands won't authenticate against ${envHost} until you point the
+  CLI there. Set this in your shell first, then re-run:
+
+    export OVERSCORE_HUB_URL=${envBase}
+
+  (Add it to ~/.zshrc to make it stick. A new terminal without it goes back to prod.)
+`);
+    process.exit(1);
+}
 function slugify(input) {
     return input
         .toLowerCase()
@@ -2397,6 +2440,10 @@ async function dev() {
         console.error("\n  Error: VITE_OVERSCORE_PROJECT_SLUG not set in .env.\n");
         process.exit(1);
     }
+    // Stop now if the dashboard's hub doesn't match where the CLI is pointed —
+    // otherwise we'd mint a key against the wrong hub and the browser would get
+    // "Invalid API key".
+    assertHubMatchesEnv();
     // Get device token from global config
     const configPath = path.join(process.env.HOME || "", ".overscore", "config");
     if (!fs.existsSync(configPath)) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@overscore/cli",
-  "version": "0.13.11",
+  "version": "0.13.12",
   "description": "CLI for deploying Overscore dashboards and publishing analyses",
   "bin": {
     "overscore": "dist/index.js"