@nemus-cli/nemus 0.3.3 → 0.4.0

package/CHANGELOG.md

@@ -7,6 +7,20 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.4.0] - 2026-09-01
+
+### Changed
+
+- **First-time setup now runs right after install.** On a fresh `npm install -g`
+  in an interactive terminal, the postinstall step launches `nemus configure`
+  automatically (it installs the shell integration + optional MCP server and
+  prints the activation reminder) instead of only suggesting you run it. It runs
+  **only on a first install** (skipped once `~/.nemus/config.json` exists, so
+  upgrades never re-prompt) and **only when a controlling terminal is reachable**
+  (via `/dev/tty`, since npm pipes postinstall stdio) — piped/scripted/CI installs,
+  or `NEMUS_SKIP_CONFIGURE=1`, fall back to the previous non-interactive path
+  (shell integration + a printed tip), so an install can never hang.
+
 ## [0.3.3] - 2026-08-30
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nemus-cli/nemus",
-  "version": "0.3.3",
+  "version": "0.4.0",
   "workspaces": [
     "packages/*"
   ],

package/scripts/postinstall.js

@@ -12,8 +12,9 @@
 
 'use strict';
 
-const { execSync } = require('child_process');
+const { execSync, execFileSync } = require('child_process');
 const fs = require('fs');
+const os = require('os');
 const path = require('path');
 
 // Skip in CI environments
@@ -21,6 +22,72 @@ if (process.env.CI) process.exit(0);
 
 const PKG_ROOT = path.join(__dirname, '..');
 const SHELL_SCRIPT = path.join(PKG_ROOT, 'install-shell-integration.sh');
+const CLI_BIN = path.join(PKG_ROOT, 'bin', 'workspace.js');
+
+// ── First-time interactive setup ─────────────────────────────────────────────
+// On a FRESH install, run `nemus configure` right away so setup happens after
+// install instead of the user having to remember to. `configure` is a superset
+// of this script's work — it installs the shell integration + (optionally) the
+// MCP server and prints the source reminder — so on success we exit here.
+//
+// npm runs postinstall with stdio PIPED (not a TTY) unless `--foreground-scripts`
+// is set, so we can't gate on process.std*.isTTY (it's falsy during a normal
+// `npm i -g`, so the prompt would never fire). Instead we reach the controlling
+// terminal directly via /dev/tty — openable during an interactive install even
+// though npm piped our own stdio — and wire configure's stdio to it. With no
+// controlling terminal (piped/scripted installs) the open fails and we fall
+// through to the non-interactive tip path, so an install can never hang.
+function cacheDir() {
+  return (
+    process.env.NEMUS_CACHE_DIR ||
+    process.env.WORKSPACE_MANAGER_CACHE_DIR ||
+    path.join(os.homedir(), '.nemus')
+  );
+}
+
+// NEMUS_SKIP_CONFIGURE opts out — but only for real values: `0`/`false`/empty do
+// NOT skip (a user setting `=0` means "don't skip").
+function optedOut() {
+  const v = (process.env.NEMUS_SKIP_CONFIGURE || '').trim().toLowerCase();
+  return v !== '' && v !== '0' && v !== 'false';
+}
+
+// The config marker `configure` writes (utils/config.ts: saveUserConfig ->
+// <NEMUS_CACHE_DIR|WORKSPACE_MANAGER_CACHE_DIR|~/.nemus>/config.json). Same
+// precedence as here, so its presence reliably means "already configured".
+function alreadyConfigured() {
+  return fs.existsSync(path.join(cacheDir(), 'config.json'));
+}
+
+// A read/write fd on the controlling terminal, or null if there isn't one.
+function openControllingTty() {
+  if (process.platform === 'win32') return null; // no /dev/tty; shell integration is bash/zsh anyway
+  try {
+    return fs.openSync('/dev/tty', 'r+');
+  } catch {
+    return null;
+  }
+}
+
+if (!optedOut() && fs.existsSync(CLI_BIN) && !alreadyConfigured()) {
+  const tty = openControllingTty();
+  if (tty !== null) {
+    try {
+      // argv form (no shell) so an odd package path with quotes/$/backticks is
+      // safe; stdio wired to the real terminal so inquirer can prompt.
+      // process.execPath (not 'node') — node may not be on PATH during a
+      // lifecycle script (nvm/Windows), and an ENOENT here would be swallowed by
+      // the catch, silently skipping configure in the very case this targets.
+      execFileSync(process.execPath, [CLI_BIN, 'configure'], { stdio: [tty, tty, tty] });
+      fs.closeSync(tty);
+      process.exit(0); // configure handled shell integration + reminder
+    } catch {
+      try { fs.closeSync(tty); } catch { /* ignore */ }
+      // Canceled / failed — fall through to the standard setup + tip below so the
+      // install still leaves things in a working state.
+    }
+  }
+}
 
 const shell = process.env.SHELL || '';
 const shellType = shell.endsWith('/zsh') ? 'zsh'