Repository navigation
Replies: 1 comment
|
dist-tag 的证据对上了:latest 还停在 0.2.1-alpha.2。 我查了 npm registry: 仓库侧也能对上:这个插件在随包的 on-demand 清单里( 治本建议和你说的一致:把 这段可以交给 AI,让它按你的版本核对;如果这条对你有用,可以标成 answer,后面遇到同样问题的人更容易找到。 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Environment
Steps to reproduce
boots to a state where no workspace can be selected.
Recovery
Removing the package and restoring the previous profile folder makes it work again.
Evidence
("the change replaces a package the DSH installation provides").
dsh-brand, dsh-experimental-session-search, dsh-session-query-sqlite,
dsh-tool-session-query, cosmokit, schemastery.
dsh-session-query and dsh-session-projection — package names from the 0.2.1 line.
Guess at the cause
Mixing 0.2.1-era @deepseek-ai packages (installed into the profile) with the 0.2.2-rc.5
runtime likely breaks plugin resolution/initialization partway, and the web UI fails to
initialize the workspace picker.
Suggestion
Declare an engines/peer version ceiling so the experimental plugin refuses to install on
newer runtimes, or ship a 0.2.2-compatible build.
Related: #10034 (same plugin, SESSION_QUERY_PERSISTENCE_FAILED on 0.2.1-rc.2).
Update — root cause found: this is a dist-tag problem, not a broken plugin.
npm view @deepseek-ai/dsh-experimental-session-search dist-tagsgiveslatest = 0.2.1-alpha.2, next = 0.2.2-rc.5.
plugin installtherefore pulls 0.2.1-alpha.2 onto a 0.2.2-rc.5 install.0.2.1-alpha.2 declares peer @deepseek-ai/cordis ~4.0.5-alpha.1 and pulls the 0.2.1 line of
dsh-session-query-sqlite / dsh-tool-session-query; those conflict with the 0.2.2 runtime,
and the workspace picker dies after restart.
matching build.
plugin install @deepseek-ai/dsh-experimental-session-search@0.2.2-rc.5latestto the 0.2.2 line, or drop it so a version must be givenexplicitly.
All reactions