dsh plugin exec cannot resolve installation peers before the first profile launch #5537
Unanswered
franksong2702
asked this question in
Q&A
Replies: 0 comments
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.
DSH 0.1.2-rc.1 can leave a freshly installed plugin command unable to resolve peer packages supplied by the DSH installation.
Reproduction
@deepseek-ai/schemasteryas a peer.dsh plugin --profile <profile> exec <bin>.The command fails with:
A profile launch first makes the same command succeed.
Cause
Profile launch prepares
$DSH_HOME/profiles/node_modules, the shared fallback containing installation-provided packages. Thedsh pluginpnpm forwarder did not prepare that fallback, so a plugin executable invoked before the first launch could not resolve its DSH-provided peers.Proposed fix
Prepare the installation module fallback after profile initialization and before forwarding every
dsh plugincommand. A self-contained built-bin regression installs a fixture with a Schemastery peer and executes it immediately.Reference implementation: franksong2702@c90ea79
Verification
All reactions