deepseek-cli-mode 1.0.1 → 1.0.2

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 1.0.2 — runtime discovery fixes
+
+- `resolveDshBin()` now also looks for `@deepseek-ai/dsh` next to this package (same `node_modules`) and in the
+  `node_modules` of every directory on `PATH`. This fixes "cannot find @deepseek-ai/dsh" when dsh is installed under a
+  custom npm prefix (including Windows drive-relative prefixes such as `E:\root\.npm-global`).
+- The not-found message now explains the Windows drive-relative `prefix=/root/.npm-global` pitfall and points at
+  `npm root -g`.
+
 ## 1.0.1 — security fixes
 
 Fixes from an independent security audit (Cloudflare `security-audit` skill, quick profile).

package/bin/deepseek.js

@@ -12,7 +12,7 @@ import { spawn, spawnSync } from "node:child_process";
 import { existsSync, mkdirSync, readFileSync, writeFileSync } from "node:fs";
 import { createRequire } from "node:module";
 import { homedir } from "node:os";
-import { dirname, join, resolve } from "node:path";
+import { dirname, delimiter, join, resolve } from "node:path";
 import { fileURLToPath } from "node:url";
 
 const here = dirname(fileURLToPath(import.meta.url));
@@ -81,6 +81,9 @@ Requires a local install of @deepseek-ai/dsh (npm i -g @deepseek-ai/dsh).`);
 function resolveDshBin() {
   const candidates = [
     process.env.DSH_CLI_DSH_BIN,
+    // Sibling install: dsh next to this package in the same node_modules.
+    // This is the normal layout when both were installed with one npm prefix.
+    join(root, "..", "@deepseek-ai", "dsh", "lib", "bin.js"),
     // Same global prefix as this node binary (npm default layout).
     join(dirname(process.execPath), "node_modules", "@deepseek-ai", "dsh", "lib", "bin.js"),
     // Common global prefixes.
@@ -96,6 +99,14 @@ function resolveDshBin() {
     candidates.push(join(process.cwd(), "node_modules", "@deepseek-ai", "dsh", "lib", "bin.js"));
   }
   for (const candidate of candidates) if (existsSync(candidate)) return candidate;
+  // npm's own bin directories are on PATH; check their sibling node_modules.
+  // This covers custom prefixes (and Windows drive-relative prefixes) that the
+  // fixed candidates above cannot know about.
+  for (const dir of String(process.env.PATH ?? "").split(delimiter)) {
+    if (dir === "") continue;
+    const candidate = join(dir, "node_modules", "@deepseek-ai", "dsh", "lib", "bin.js");
+    if (existsSync(candidate)) return candidate;
+  }
   // Resolve only from this package's own module graph (never from cwd).
   try {
     return requireFromHere.resolve("@deepseek-ai/dsh/lib/bin.js");
@@ -204,8 +215,10 @@ const dshBin = resolveDshBin();
 if (dshBin === undefined) {
   console.error(
     "deepseek: cannot find @deepseek-ai/dsh.\n" +
-      "  Install it once:  npm i -g @deepseek-ai/dsh\n" +
-      "  Or point DSH_CLI_DSH_BIN at .../@deepseek-ai/dsh/lib/bin.js"
+      "  Install it once in the same npm prefix as this CLI:  npm i -g @deepseek-ai/dsh\n" +
+      "  Or point DSH_CLI_DSH_BIN at .../@deepseek-ai/dsh/lib/bin.js\n" +
+      "  If it is installed but not found, check `npm root -g` (a POSIX-style npm prefix such as\n" +
+      "  /root/.npm-global resolves per drive on Windows; use C:\\... instead)."
   );
   process.exit(1);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "deepseek-cli-mode",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "description": "Terminal (CLI) mode for DeepSeek Harness — an interactive, Claude Code-style coding agent for your shell.",
   "type": "module",
   "main": "index.js",