dsh-client-fix

If you keep hitting the cryptic "system cannot find the specified path" error when installing plugins through DSH Desktop, the root cause is almost always an encoding mismatch. The desktop app writes its pnpm shim file in UTF-8, but cmd.exe on Windows interprets it under GBK (code page 936). Any Chinese character in the install directory (for example D:\Software...) gets mangled into an unreadable path, and the command fails outright. dsh-client-fix detects this within three seconds of startup and injects a chcp 65001 directive into the shim so the path resolves correctly regardless of the active code page. If the desktop application restarts and regens the broken shim, the plugin automatically repairs it again with zero manual effort.

Beyond the encoding fix, the plugin establishes a one-way real-time sync channel from the desktop profile to the web profile. It uses fs.watch to monitor the desktop package.json and pnpm-lock.yaml, applies an 800 ms debounce, then reconciles the web side to mirror desktop exactly: plugins present on desktop but missing on web get installed, plugins already removed from desktop get uninstalled from web, and any version drift is corrected to match desktop. Market updates only touch the desktop profile; the web side follows automatically, eliminating the need to manually keep two plugin lists in lockstep.

The plugin also pre-writes the target pkg@version into minimumReleaseAgeExclude in pnpm-workspace.yaml before installation, preventing pnpm from rejecting freshly published packages with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION. This is ideal for Windows users whose DSH Desktop lives under a Chinese-language path and who want their desktop and web plugin inventories to stay perfectly aligned without any ongoing bookkeeping.