dsh-better-plugin-updater

Q: Does it collide with dshmarket?

dsh-better-plugin-updater is the one to keep here: It only plans and never applies without approval, so it is the safer writer to keep when you want version control.

Q: Which dsh versions load it, and what happens outside that window?

On >=0.2.1-rc.4 <0.3.0 the CLI loads dsh-better-plugin-updater; outside it, boot stops with the requirement instead of running the plugin. dsh plugin allow-version dsh-better-plugin-updater is the per-package override if you accept the risk.

Manual multi-source update checks with a plan you approve before anything changes.

Version 0.1.2 of dsh-better-plugin-updater, last published 2026-11-13; the install command and the range come from its own manifest.

Install

dsh plugin add dsh-better-plugin-updater writes one dependency line into the profile manifest; pnpm then unpacks it under $DSH_HOME/profiles/<name>/node_modules.

dsh plugin --profile web add dsh-better-plugin-updater

Compatibility

engines.dsh in dsh-better-plugin-updater declares >=0.2.1-rc.4 <0.3.0; run dsh --version and compare it, because outside that range the CLI skips the plugin at boot and prints the requirement instead of booting.

If two plugins fight

Writes package versions into the profile. dshmarket and universal-plugin-hub write the same package.json, so an update can be planned from one UI and clobbered by an install from another.

Who made it

Author: Mooling0602. Repository: https://github.com/Mooling0602/dsh-better-plugin-updater. Package page: https://www.npmjs.com/package/dsh-better-plugin-updater.

After install

It declares @deepseek-ai/cordis as a peer and renders a plugin browser in the left sidebar; after dsh plugin add dsh-better-plugin-updater, dsh --profile web --dump-config lists the row that mounts it.

Files it touches

No storage peer appears in the manifest of dsh-better-plugin-updater, so the dependency line in $DSH_HOME/profiles/<name>/package.json is the only file you can point at; the package description names nothing else.

Removing it

Removing dsh-better-plugin-updater is the mirror command, dsh plugin --profile web remove dsh-better-plugin-updater. Its manifest declares no storage peer, so it writes nothing under $DSH_HOME; removing it leaves no files behind.

Common questions

Does it collide with dshmarket?

dsh-better-plugin-updater is the one to keep here: It only plans and never applies without approval, so it is the safer writer to keep when you want version control.

Which dsh versions load it, and what happens outside that window?

On >=0.2.1-rc.4 <0.3.0 the CLI loads dsh-better-plugin-updater; outside it, boot stops with the requirement instead of running the plugin. dsh plugin allow-version dsh-better-plugin-updater is the per-package override if you accept the risk.