dsh-web-ui#packages/dsh-web-ui-all

@linxin666/dsh-web-ui-all

English | 中文

The one-click aggregate package for the whole dsh web UI family: installing it brings every functional plugin (task-board / git-graph / pet / remote-web-ui / web-ui-settings / skin-center / community-plugins / aionui-panel) plus the external plugins dsh-better-sidebar (right panel) and @mlgbnb/dsh-archive-manager (settings-page archive manager) and the skin family (dsh-skins, skin assets bundled inside). The compat bridge layer is folded into this package (src/client), so no separate compat npm package is needed.

What it is

• One install, everything on: its dependencies pull in all sub-plugin packages (dsh-client-ui-aionui-panel / dsh-client-ui-task-board / dsh-client-ui-git-graph / dsh-pet / dsh-remote-web-ui / dsh-ssh / dsh-client-ui-web-ui-settings / dsh-client-ui-skin-center / dsh-client-ui-community-plugins / dsh-skins) plus the external npm plugins dsh-better-sidebar (the default right sidebar: explorer / editor / terminal / git / browser) and @mlgbnb/dsh-archive-manager (the default settings-page archive manager: group by project, search and filter, preview conversations, restore and delete).
• Aggregation carrier: cordis.patch.yml aggregates the insert lines of each sub-plugin plus the external dsh-better-sidebar and @mlgbnb/dsh-archive-manager rows, mounted through the dsh plugin profile mechanism.
• Right panel: the right panel is always dsh-better-sidebar (the aionui panel can no longer be enabled). Settings → Web UI Plugins → Side Card declares the right panel comes from dsh-better-sidebar and edits its everyday settings inline; the provider choice was removed.

Install

From npm (recommended)

dsh plugin --profile web add @linxin666/dsh-web-ui-all@latest

From the repository (development)

git clone https://github.com/zhu1090093659/dsh-web-ui.git
cd dsh-web-ui
pnpm install && pnpm -r build
node scripts/link-profile.mjs
dsh plugin --profile web add link:$(pwd)/packages/dsh-web-ui-all

Restart dsh web for the plugins to take effect.

Manual upgrade

When you upgrade by bumping the version in the profile package.json and running pnpm install, the top-level node_modules/@linxin666/* entries are not always refreshed: they can stay linked to the previous version's store directory until recreated. After upgrading, verify the links resolve to the new version (on Windows: cmd /c rmdir <link> then cmd /c mklink /J <link> <target>), then restart dsh web.

Troubleshooting

"Failed to load plugins ... keyed slot settings.plugin.item requires options.key" (DSH 0.1.0-rc.6+)

Versions up to 0.1.17 of the bundled dsh-client-ui-web-ui-settings registered its card in the keyed settings.plugin.item slot with an id instead of the required key (the other family plugins already registered their cards in the group's list slot). DSH 0.1.0-rc.6 and later reject such entries while the loader entry applies, so the web GUI fails to boot with "Failed to load plugins".

The group moved to a first-level settings.section registration in 0.1.18 and ships in 0.2.0; the code on main is compatible with rc.6 and rc.7. A profile that still fails carries a frozen older install:

1. Bump every @linxin666/* dependency in the profile package.json to ^0.2.0 (at least ^0.1.18).
2. Reinstall the profile dependencies (pnpm install) and recreate the stale node_modules/@linxin666/* links as described in Manual upgrade above.
3. Restart dsh web.

See issue #513.

Known limitations

• Every sub-plugin activates together. For only a subset, install that sub-plugin package directly.
• Aggregate rows are namespaced web-ui-*, so the bundle can coexist with a standalone install of the same plugin: the loader no longer rejects the duplicate id, the host half runs once (the second source is a no-op), and the browser half is deduped by package name. Keeping both sources has no benefit; prefer one. When the bundle is the source, profile patch config rows must use the web-ui-* id (e.g. web-ui-remote-web-ui for the remote-web-ui autoTunnel row); standalone installs keep the plugin's own id.
• dsh-better-sidebar and @mlgbnb/dsh-archive-manager are external npm dependencies (not authored in this repo); they must be published before this package's release (see docs/publish-prep.md for the release order).
• Dependencies on the @deepseek-ai/* SDK are pinned; compatibility follows the repository's release cadence.