Repository navigation
v1.4.13 — a missing dependency no longer looks like a broken plugin
v1.4.13 — a missing dependency no longer looks like a broken plugin
DSH Plugin Hub is the community plugin marketplace for DeepSeek Harness. This release fixes how a failed install is diagnosed: when a package recorded in your profile is missing from the npm registry, the marketplace used to report the plugin you were installing as incompletely distributed, and offered to open an issue against it.
Website: dsh-plugin.org
What's New
-
The plugin you were installing is no longer blamed for another package's 404 — A package missing from the npm registry is now recognised as a problem of the profile it is recorded in, not of the plugin being installed. Previously any such failure was reported as "plugin distribution incomplete", pointing the report at whichever plugin was being installed at the time (#73).
-
Missing dependencies are now named, with the fix — The failure dialog states which package does not exist on the registry and asks you to remove that entry from the profile's
package.json(and its lockfile entry), instead of offering to report an issue against an unrelated plugin (#73). -
The error code in failure reports is no longer truncated — Codes containing digits were cut off before, so
ERR_PNPM_FETCH_404reached the report asERR_PNPM_FETCH_(#73).
Thanks to @xiangyu0 for the report and environment notes.
Installation
Option 1 · via npm (recommended):
dsh plugin --profile web add dsh-pluginOption 2 · via the official GitHub repository:
dsh plugin --profile web add git+https://github.com/dshplugin/dsh-plugin-hub.git