dsh web fails after global pnpm install: loader cannot resolve ~88 plugin packages

[yamsfeer]

Describe the bug

Installing @deepseek-ai/dsh as a global pnpm package and running dsh web fails to boot: the Cordis loader cannot resolve most plugin packages, producing a very long error dump.

Environment

• dsh 0.1.0-rc.6 (installed via pnpm add -g @deepseek-ai/dsh@0.1.0-rc.6)
• pnpm v11.17.0
• Node v24.x
• macOS

To reproduce

pnpm add -g @deepseek-ai/dsh@0.1.0-rc.6
dsh web

Expected: boots and prints dsh web: http://127.0.0.1:<port>.

Actual: a long stack trace ending in

Error: dsh: plugin tree failed to load: failed to apply loader entry include (cordis:include): loader entries failed to apply

with a list of errors like:

Error: failed to import loader entry timer (@deepseek-ai/cordis-plugin-timer): Cannot find package '@deepseek-ai/cordis-plugin-timer' imported from .../@deepseek-ai/cordis-plugin-loader/lib/index.js
Error: failed to import loader entry llm (@deepseek-ai/dsh-llm): Cannot find package '@deepseek-ai/dsh-llm' imported from .../@deepseek-ai/cordis-plugin-loader/lib/index.js
Error: failed to import loader entry session (@deepseek-ai/dsh-session): Cannot find package '@deepseek-ai/dsh-session' imported from .../@deepseek-ai/cordis-plugin-loader/lib/index.js

…and similar for ~88 packages (126 packages needed by the web profile, only 59 resolvable).

Root cause analysis

Two independent issues combine under pnpm's global (symlinked) install layout:

1. healProfilesModuleFallback cannot traverse the transitive dependency closure

healProfilesModuleFallback in dsh-app-boot maintains the flat fallback dir $DSH_HOME/profiles/node_modules (one symlink per package in the app's dependency closure). It resolves each package with packageDirFromAnchor, which uses createRequire(anchor).resolve.paths(...) — a string-path probe that does not follow symlinks.

Under pnpm's global layout, dsh's direct dependencies resolve fine (they sit next to the app), but the transitive deps of bundle packages (e.g. dsh-web-app's deps like dsh-llm, dsh-session, dsh-host-webserver, dsh-typert-registry, …) live inside the pnpm content store and are not reachable from the symlink anchor, so the BFS silently drops them. Only ~59 direct deps get linked; the ~88 packages required by the web profile are missing from the fallback dir.

2. Loader requires --expose-internals for baseUrl-based plugin resolution

cordis-plugin-loader's import() uses the internal Node ESM loader (which imports from ctx.baseUrl, i.e. the profile dir) only when ModuleLoader.fromInternal() succeeds, which requires the --expose-internals flag on the node process. Otherwise it falls back to plain ESM import() (external mode), which resolves relative to the loader's own location inside the pnpm store — where the plugin packages don't exist.

The pnpm-generated bin shim for dsh does not pass --expose-internals, so even with all symlinks in place, plugin resolution still fails.

Workaround (local, not a fix)

• Symlink the ~88 missing packages from the pnpm content store into $DSH_HOME/profiles/node_modules/@deepseek-ai/ (plus 2 hidden include-referenced deps: dsh-host-directory-picker-native, dsh-client-ui-directory-picker-native), and
• patch the pnpm bin shim to invoke node --expose-internals.

Suggested fixes

1. In healProfilesModuleFallback / packageDirFromAnchor: resolve symlinks (realpath) before probing, so the transitive closure is found under pnpm's symlinked layouts.
2. Make the dsh entrypoint always run with --expose-internals (shebang or shim), or make the loader's baseUrl-based (internal) import the default instead of an opt-in.

This makes the tool unusable for the most common install path (pnpm add -g), so it would be great to have it fixed before the stable release.

[xw901103]

manually install them with pnpm

pnpm -w i @deepseek-ai/cordis-plugin-timer
pnpm -w i @deepseek-ai/dsh-llm
pnpm -w i @deepseek-ai/dsh-session

if you git cloned them from this repo, all these packages should be located inside the deepseek-harness\packages workspaces, you should not need to manually do anything.

[sanxiu-snowfield]

clear your npx cache by "npx clear-npx-cache "
then update your nodejs to newest version, its work for me