npm dist-tags: latest still points at 0.0.1-rc.1 builds with unresolvable dependencies

[JUANWANG-BUAA]

Summary

As of 2026-08-16, the npm latest dist-tags for the @deepseek-ai packages point at 0.0.1-rc.1 builds whose dependencies do not resolve, so the documented install command fails out of the box:

dsh plugin add @deepseek-ai/dsh-web-app   # resolves latest → 0.0.1-rc.1 → 404 on deps

Details (verified against the registry today)

npm view @deepseek-ai/dsh-web-app dist-tags → { latest: '0.0.1-rc.1', next: '0.1.0-rc.6' }

@deepseek-ai/dsh-web-app@0.0.1-rc.1 declares 9 dependencies that do not exist on the registry:

• @deepseek-ai/dsh-frontend
• @deepseek-ai/dsh-client-ui-model
• @deepseek-ai/dsh-client-ui-slash
• @deepseek-ai/dsh-frontend-static
• @deepseek-ai/dsh-client-ui-models
• @deepseek-ai/dsh-client-ui-command
• @deepseek-ai/dsh-client-ui-question
• @deepseek-ai/dsh-code-runtime-worker
• @deepseek-ai/dsh-client-ui-permission

Pinning the next version works: @deepseek-ai/dsh-web-app@0.1.0-rc.6 resolves all of its dependencies.

The same pattern affects other packages — @deepseek-ai/dsh-client-runtime, @deepseek-ai/dsh-client-ui-layout, @deepseek-ai/dsh-client-ui-sidebar, @deepseek-ai/dsh-client-ui-slots, @deepseek-ai/dsh-message-feedback all have latest stuck at 0.0.1-rc.x.

Impact

Several community plugins document "the official web bundle is not published to npm" and tell users to install it from a source checkout. That workaround is unnecessary: the packages are published, the latest tag just points at broken pre-rc builds.

Ask

• Move the latest dist-tag (for dsh-web-app at least, ideally the whole @deepseek-ai set) to the current 0.1.0-rc.6 line, or
• Publish fixed versions of the 9 unresolvable dependencies under 0.0.1-rc.1.