@cairnvibe/indexer 0.2.9 → 0.2.10

package/dist/setup.js

@@ -171,8 +171,21 @@ async function runSetup(dir) {
             (0, node_child_process_1.execSync)(`npm install ${PACKAGES.join(" ")}`, { cwd: absDir, stdio: "pipe" });
             spinner.stop((0, ui_1.green)(`✓ installed ${PACKAGES.join(", ")}`));
         }
-        catch {
+        catch (err) {
             spinner.stop((0, ui_1.red)("✗ npm install failed"));
+            // Real, live-found bug this closes: `catch {}` (no bound error) threw
+            // away npm's own stderr — the ONE thing that actually explains why it
+            // failed (a real registry error, an ERESOLVE conflict, a permissions
+            // problem, no network) — leaving a user with nothing but "failed, try
+            // again," which just fails the same way for the same unknown reason.
+            // execSync's thrown error carries the captured output on
+            // `.stderr`/`.stdout` (Buffers, from the `stdio: "pipe"` above) even
+            // though the command itself never printed anything to this process's
+            // own stderr — surface it instead of discarding it.
+            const e = err;
+            const detail = (e.stderr?.toString().trim() || e.stdout?.toString().trim() || "").trim();
+            if (detail)
+                console.error(`\n${detail}\n`);
             console.error(`Install these yourself and re-run \`cairn setup\`:\n  npm install ${PACKAGES.join(" ")}`);
             return;
         }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cairnvibe/indexer",
-  "version": "0.2.9",
+  "version": "0.2.10",
   "description": "Cairn's analyzer and installer (the `cairn` CLI) — scans Next.js source or crawls any running app, and scaffolds the backend either way.",
   "license": "MIT",
   "publishConfig": { "access": "public" },