[Bug] npm 安装的 dsh 闭包缺少 @deepseek-ai/dsh-client-schema-form,引用它的第三方插件启动即崩溃

[fan56]

TL;DR: npm i -g @deepseek-ai/dsh 安装的 dsh(0.1.0-rc.6 ~ rc.8 均复现)全局闭包缺少 @deepseek-ai/dsh-client-schema-form,按闭包契约 import 该包的第三方插件在全新环境启动即抛 Cannot find package 崩溃;Homebrew 安装的同版本 dsh 闭包则包含该包 —— 两个分发渠道闭包内容不一致。

摘要 / Summary

• npm 版 dsh 的全局闭包($(npm root -g)/@deepseek-ai/dsh/node_modules/@deepseek-ai/,共 195 个 @deepseek-ai/* 包)中没有 dsh-client-schema-form;
• Homebrew 版 dsh 0.1.0-rc.6(同版本号)闭包中有 dsh-client-schema-form@0.1.0-rc.6;
• 插件按 dsh 闭包契约(所有 @deepseek-ai/* 解析到同一闭包,profile 侧由 healProfilesModuleFallback 软链)import 该包时,npm 分发下启动即崩:

Error: failed to apply loader entry include (cordis:include): failed to import loader entry
tui-pi (@aiwayds/dsh-tui-pi): Cannot find package '@deepseek-ai/dsh-client-schema-form'
imported from ~/.dsh/profiles/tui/node_modules/@aiwayds/dsh-tui-pi/lib/settings.js

排查与根因 / Root Cause

monorepo 中该包位于 packages/client/schema-form(HEAD 版本 0.1.0-rc.7),但引用它的包(packages/client/ui-settings、ui-settings-models、ui-permission-presets、web 等)全部以 peerDependencies: "workspace:^" 方式声明;而发布的 apps/cli(即 npm 上的 @deepseek-ai/dsh)自身 61 个 dependencies 也不含它。于是:

• monorepo 内 workspace 解析照常工作;
• Homebrew 打包带上完整 workspace 闭包 → 有该包;
• npm 分发只按 apps/cli 的依赖图安装 → peer 依赖无人提供 → 缺件。

第三方插件无法通过在自己的 dependencies 里声明来规避:插件契约要求所有 @deepseek-ai/* 解析到同一个闭包,自装会引入第二份实例。

复现 / Reproduction(Ubuntu 22.04 容器)

podman run -it ubuntu:22.04 bash
# 安装 node 22 + pnpm 10 后:
npm i -g @deepseek-ai/dsh@0.1.0-rc.7 pnpm@10        # rc.6 / rc.8 同样复现
dsh plugin --profile tui add @aiwayds/dsh-tui-pi@0.8.0
dsh --profile tui                                     # ← 启动即崩,报上面的 Cannot find package

# 验证闭包缺件:
ls $(npm root -g)/@deepseek-ai/dsh/node_modules/@deepseek-ai | grep schema-form   # 空

macOS Homebrew 对照(同版本不崩):

$ ls /opt/homebrew/lib/node_modules/@deepseek-ai/dsh/node_modules/@deepseek-ai | grep schema-form
dsh-client-schema-form

临时规避 / Workaround

向 profile 补装独立发布的包(注意其 npm latest dist-tag 停在 0.0.1-rc.1,新版本在 next):

cd ~/.dsh/profiles/<profile>
pnpm add @deepseek-ai/dsh-client-schema-form@next    # 0.1.0-rc.7

建议 / Suggestion

1. apps/cli 的 dependencies 增加 @deepseek-ai/dsh-client-schema-form(或将 ui-settings 对它的 peer 声明提升为 dependency),保证 npm 分发闭包完整;
2. 顺带排查闭包内其他"仅以 peerDependencies: workspace:^ 声明"的包是否存在同样缺口;
3. @deepseek-ai/dsh-client-schema-form 的 latest dist-tag 指向 0.0.1-rc.1 而最新发布为 0.1.0-rc.7(在 next),建议对齐,避免规避安装拿到旧版。

受影响的真实消费者:@aiwayds/dsh-tui-pi(自 0.7.2 起 settings 面板使用 schema-form,全新容器/DSH_HOME 必崩,补装后恢复正常)。

[denial123789]

One additional release-boundary detail may help make the workaround reproducible:

• at the official rc.8 commit (141eb6f), the CLI manifest does not declare @deepseek-ai/dsh-client-schema-form, and that package is not present in the rc.8 tagged source tree;
• npm currently reports latest=0.0.1-rc.1 and next=0.1.0-rc.7, with no rc.8 schema-form publication.

That means pnpm add ...@next places an rc.7 internal package into an rc.8 profile. It is useful as a disposable compatibility probe, but it should not yet be treated as a general production repair: pin the exact version, verify that all @deepseek-ai/* runtime packages still resolve from the intended closure, then test profile boot, plugin settings, core settings, reload, and restart. A compatible plugin release or a DSH distribution that carries the coherent closure remains safer.

I turned the evidence routing and acceptance gates into a source-linked runbook here: https://sandbaseai.github.io/deepseek-harness-handbook/missing-client-schema-form.html