@deepseek-ai/dsh@0.1.3-alpha.2 cannot be installed without a C++ toolchain: new hard dependency fs-ext (node-gyp, no prebuilt binaries)

[vollegrewar]

Problem

On a Windows machine without Visual Studio C++ build tools, npm install @deepseek-ai/dsh@0.1.3-alpha.2 fails during dependency installation.

Root cause

• dsh-session-persistence-jsonl@0.1.3-alpha.2 gained a required dependency on fs-ext@2.1.1 (pinned to the exact version).
• fs-ext's install script is node-gyp configure build — it ships no prebuilt binaries (no prebuild-install, no binary field in its manifest).
• Without a VS C++ toolchain, node-gyp fails with Could not find any Visual Studio installation to use, and the whole dependency install fails.

Repro

$ npm install @deepseek-ai/dsh@0.1.3-alpha.2
npm error gyp ERR! find VS **************************************************************
npm error gyp ERR! find VS You need to install the latest version of Visual Studio
npm error gyp ERR! find VS including the "Desktop development with C++" workload.
npm error gyp ERR! find VS **************************************************************
npm error gyp ERR! configure error
npm error gyp ERR! stack Error: Could not find any Visual Studio installation to use

Environment: Windows 11 (10.0.26200), Node v22.23.1, node-gyp v11.5.0, npm (registry configured to npmmirror).

Background

This is the second consecutive npm release that cannot be installed:

• 0.1.2-rc.1: the four experimental packages (@deepseek-ai/dsh-experimental-agent-team and friends) were never published to npm — every fresh install fails with 404.
• 0.1.3-alpha.2: adds a native hard dependency (fs-ext) with no prebuilt binaries — machines without a C/C++ toolchain cannot install it at all.

For comparison, the 0.1.1 line's dsh-session-persistence-jsonl used koffi, which ships prebuilt binaries and installs cleanly on Windows. The 0.1.3-alpha.2 switch to fs-ext regressed that.

Suggestions

1. Make fs-ext optional / degrade gracefully, or switch to an alternative that ships prebuilt binaries (the prebuilt route, like koffi).
2. Or ship prebuilt binaries for fs-ext (at least the common platforms such as win32-x64).
3. At minimum: call out the C++ toolchain as a hard prerequisite in the release/install docs, and fail at install time with clear guidance — the current error just says "install VS", which is unfriendly to pure consumers who never compile anything.

This belongs to the same class as the existing node-pty native-module discussions (#605, #835, #1245) — "native modules without prebuilt binaries break installs". A systematic fix (a unified prebuild strategy or a graceful-degradation path) would help all of them.

(Posted by a dsh user on Windows; happy to provide the full npm debug log on request.)

[vollegrewar]

中文翻译 / Chinese translation

---

标题：@deepseek-ai/dsh@0.1.3-alpha.2 在无 C++ 工具链的机器上无法安装：新增硬依赖 fs-ext（node-gyp 原生模块，无预编译二进制）

问题

Windows 机器（未安装 Visual Studio C++ 构建工具）上，npm install @deepseek-ai/dsh@0.1.3-alpha.2 在依赖安装阶段失败。

根因

• dsh-session-persistence-jsonl@0.1.3-alpha.2 新增了必需依赖 fs-ext@2.1.1（精确版本）
• fs-ext 的安装脚本是 node-gyp configure build，不提供任何预编译二进制（无 prebuild-install、manifest 中无 binary 字段）
• 没有 VS C++ 工具链 → node-gyp 报 Could not find any Visual Studio installation to use → 整个依赖安装失败

复现

$ npm install @deepseek-ai/dsh@0.1.3-alpha.2
npm error gyp ERR! find VS **************************************************************
npm error gyp ERR! find VS You need to install the latest version of Visual Studio
npm error gyp ERR! find VS including the "Desktop development with C++" workload.
npm error gyp ERR! find VS **************************************************************
npm error gyp ERR! configure error
npm error gyp ERR! stack Error: Could not find any Visual Studio installation to use

环境：Windows 11 (10.0.26200)、Node v22.23.1、node-gyp v11.5.0、npm（registry 配置为 npmmirror）。

背景

这是连续第二个无法安装的 npm 发布：

• 0.1.2-rc.1：四个 experimental 包（@deepseek-ai/dsh-experimental-agent-team 等）从未发布到 npm，任何全新安装 404
• 0.1.3-alpha.2：新增无预编译二进制的原生硬依赖（fs-ext），没有 C/C++ 工具链的机器完全装不上

对比：0.1.1 线的 dsh-session-persistence-jsonl 用的是 koffi（自带预编译二进制，Windows 上可干净安装）。0.1.3-alpha.2 换用 fs-ext 是回归。

建议

1. 把 fs-ext 改为可选/优雅降级，或改用带预编译二进制的替代方案（如 koffi 的预编译路线）
2. 或为 fs-ext 提供预编译二进制（至少覆盖 win32-x64 等主流平台）
3. 至少：在发布/安装文档中明确标注 C++ 工具链是硬性前置，并在安装失败时给出清晰指引——当前报错只说"装 VS"，对从不编译代码的纯使用者不友好

这与既有的 node-pty 原生模块讨论（#605、#835、#1245）同属"无预编译原生模块破坏安装"一类，系统性解决（统一预编译策略或优雅降级路径）会对所有同类问题都有帮助。

（发布者：一位 Windows 上的 dsh 用户；如需完整 npm debug 日志可提供。）

[buddha68]

Confirmed on another clean Windows machine — same root cause, plus two data points that may help other users until this is fixed.

Reproduction (global npm path):

• Windows 11 (10.0.22631), Node v24.19.0, npm 11.17.0, node-gyp 12.4.0
• npm i -g @deepseek-ai/dsh@0.1.3-alpha.2 fails at fs-ext@2.1.1's node-gyp configure build step with "Could not find any Visual Studio installation to use"
• Standalone repro: npm i fs-ext@2.1.1 in an empty temp directory fails identically — so this is purely the missing MSVC toolchain, nothing dsh-specific.

Data point 1 — npm rollback keeps users safe: when the global install fails, npm rolls back cleanly and the previous version (0.1.2-rc.1) stays fully functional. No broken state, which softens the blast radius a lot.

Data point 2 — a workable interim combo: the latest web-all frontend (0.3.18) runs fine against the 0.1.2-rc.1 core, so Windows users can stay on rc.1 + web-all 0.3.18 while waiting for a fix, instead of rushing the alpha.

Agreed with the analysis above: if fs-ext is never actually called on win32, the cleanest fix would be dropping it from the win32 dependency tree (optional dependency / platform-conditional), rather than asking every Windows user to install a multi-GB MSVC toolchain for code that never runs.