wuwei6666/dsh-pluginguard
Isolates a plugin that throws at import so the web client still boots, and lists what else you can enable, pause or remove.
Answers a real failure mode of a plugin-heavy profile: one broken plugin crashing the whole web client at boot, with no UI left to remove it. The guard imports every user plugin entry in isolation, removes anything that throws from the boot bundles, disables it through cordis.patch.yml, and records it as damaged in dsh-plugin-guard-damage.json while everything else keeps running. It also manages the ordinary case — listing only plugins you installed yourself, with enable, pause and uninstall persisted through the patch layer — and checks npm for its own newer version with an in-place update. A standalone lib/profile-guard.js can repair a profile before the web client has started at all.
Install
dsh plugin --profile web add dsh-plugin-guardThe npm line, against the package name dsh-plugin-guard — the repo is spelled with a capital G but the registry name is not. The README also documents editing the profile's package.json by hand with dsh.profile.bundles, then running pnpm install. The tab it adds lives under Settings, Plugins, and the UI is bilingual, following the DSH language setting.
Compatibility
Two guarantees worth separating: a plugin that throws on import is quarantined rather than taking the web client down, and the guard itself is wrapped at every entry point — route try-catch, React error boundary and guarded module loading — so at worst its own tab is unavailable. It imports zero DSH runtime packages, using Node built-ins and defensive probing of the loader and slots APIs, which is what lets a harness upgrade degrade it rather than break it. Writes stay inside the user profile directory and the application install directory is never modified.
Details
- Repo: wuwei6666/dsh-pluginguard
- Category: Plugin Markets & Managers
- Stars: 1
- Version: 0.1.1 (npm)
Alternatives
lxzy-7/dsh-plugin-guard · PerryLink/dsh-plugin-upgrade · Luaphes/dsh-plugins-market