Repository navigation
Replies: 1 comment
|
Confirmed from the published artifact, including a minimal repro.
Link zod into the same tree and the module imports cleanly — so zod is the only missing link, and the generated module is otherwise sound. |
Uh oh!
There was an error while loading. Please reload this page.
Environment
@deepseek-ai/dsh0.2.2-rc.2 installed viapnpm add -g @deepseek-ai/dsh@0.2.2-rc.2Steps to reproduce
pnpm add -g @deepseek-ai/dsh@0.2.2-rc.2dsh webObserved
The web server still starts (the UI is served), so this is easy to miss — but the
ctx.webcapability (search/fetch provider registry) is never registered, and every start prints the warning.Root cause
lib/typert.host.jsstarts withimport { z } from 'zod', butpackages/web/web/package.jsondoes not declarezodat all — neither independenciesnor inpeerDependencies:The published lockfile confirms it: the
@deepseek-ai/dsh-web@0.2.2-rc.2snapshot resolves exactly cordis / dsh-llm / dsh-package-manifest / dsh-typert-protocol / schemastery — nozod. Meanwhile ~65 sibling packages (dsh-typert-protocol,dsh-agent,dsh-llm,dsh-typert-registry, …) all declarezod: 4.6.6.So under pnpm's isolated
node_moduleslayout nothing linkszodnext todsh-web, and Node resolves ESM imports against the package's real path inside the store, where no ancestornode_modulescontainszod. (Under npm's flat layout this would silently work, which is probably why it slipped through.)Suggested fix
Add
zodtopackages/web/web/package.jsondependencies, using the same specifier as the rest of the workspace (4.6.6, or the shared^4.xrange). It would also be worth grepping the workspace for other packages that importzodwithout declaring it, so this class of bug does not reappear under isolated installs.Workarounds for users on 0.2.2-rc.2
packageExtensionsin the pnpm workspace rootpnpm-workspace.yaml(pnpm >= 10 no longer reads thepnpmfield ofpackage.json):.../node_modules/.pnpm/.../node_modules/@deepseek-ai/dsh-web→ putzodalongside the package's sibling links, i.e.links/@deepseek-ai/dsh-web/<version>/<hash>/node_modules/zodpointing atlinks/@/zod/4.6.6/<hash>/node_modules/zod.Verification
After making
zodresolvable fordsh-web:import('.../dsh-web/lib/typert.host.js')succeeds and exportsTYPERTdsh webstarts with an empty stderr — no1 entry did not activate200and web access capability is registeredAll reactions