@dopemarkets/agent 0.1.2 → 0.1.3

package/dist/index.js

@@ -15,7 +15,7 @@ const markets_js_1 = require("./commands/markets.js");
 const stack_js_1 = require("./commands/stack.js");
 const agent_key_js_1 = require("./commands/agent_key.js");
 const mcp_js_1 = require("./commands/mcp.js");
-const VERSION = '0.1.2';
+const VERSION = '0.1.3';
 const HELP = `dope — DOPE Agent Mode CLI (v${VERSION})
 
 Usage:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dopemarkets/agent",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "DOPE Agent Mode CLI. Run agentic Stack trades on DOPE from the terminal.",
   "bin": {
     "dope": "bin/dope.js"

package/scripts/postinstall.js

@@ -5,20 +5,32 @@
 // unambiguous "the install succeeded — here's what to do next" line.
 // Non-developers won't otherwise know the install worked.
 //
-// Note: we tried gating this on `process.env.npm_config_global === 'true'`
-// so the banner would only appear on `-g` installs and stay quiet when
-// the package was pulled in as a transitive dep. In practice npm 11
-// does not reliably set that env var for postinstall scripts, so the
-// banner never fired on the install path that actually matters.
-// `@dopemarkets/agent` is a CLI; the global install is overwhelmingly
-// the intended use, and a stray banner on a rare local install is not
-// worth losing the signal on the common path. Always print.
+// Two non-obvious things make this trickier than it looks:
 //
-// Rules that remain:
-//   - Print to stderr so it sits alongside npm's own install chatter
-//     and never contaminates a script's stdout.
-//   - Never throw. Postinstall failures bubble up as install failures,
-//     and a banner is not worth breaking somebody's machine over.
+//   1. npm 9+ runs postinstall scripts in background mode by default
+//      (the `--foreground-scripts` flag is opt-in). In background
+//      mode npm captures the child's stdout/stderr and only surfaces
+//      them on failure. Writing to `process.stderr` is therefore
+//      invisible to the user on a normal `npm install -g` run. To
+//      reach the user's terminal we open `/dev/tty` for writing and
+//      print there, bypassing npm's stream capture entirely. This
+//      requires a controlling terminal (so e.g. CI shows nothing,
+//      which is the right outcome — no human to read the banner).
+//
+//   2. We previously tried gating this on `npm_config_global` so the
+//      banner would only print on `-g` installs. npm 11 does not
+//      reliably set that env var for postinstall scripts, so the
+//      gate silently no-op'd on the install path that actually
+//      matters. `@dopemarkets/agent` is a CLI; the global install
+//      is overwhelmingly the intended use. We always print.
+//
+// Rules:
+//   - Try the controlling TTY first (works on the common case).
+//   - Fall back to stderr (covers Windows, `--foreground-scripts`,
+//     and any environment without a usable /dev/tty).
+//   - Never throw. Postinstall failures bubble up as install
+//     failures, and a banner is never worth breaking somebody's
+//     machine over.
 
 'use strict';
 
@@ -33,7 +45,24 @@ try {
     'Run `dope --help` to see every command.',
     '',
   ];
-  process.stderr.write(lines.join('\n'));
+  const message = lines.join('\n');
+
+  let wroteToTty = false;
+  if (process.platform !== 'win32') {
+    try {
+      // Synchronous open + write so we don't leak across npm's
+      // postinstall lifecycle boundary.
+      const fs = require('fs');
+      fs.writeFileSync('/dev/tty', message);
+      wroteToTty = true;
+    } catch {
+      // No controlling TTY (e.g. CI). Fall through to stderr.
+    }
+  }
+
+  if (!wroteToTty) {
+    process.stderr.write(message);
+  }
 } catch {
   // Intentionally swallow. A banner is never worth a failed install.
 }