dshost-plugin

Q: Does it collide with ds-harness-remote?

For dshost-plugin the recommendation is ds-harness-remote: It peers dsh-api-gateway and the settings pages, which keeps the exposure beside the thing being exposed.

Q: What happens when dsh upgrades?

Nothing declares a version window for dshost-plugin: dsh --version tells you what you are running, and no check will tell you whether dshost-plugin matches it.

A relay plugin that exposes the local web UI through a hosted endpoint.

Version 0.1.25 of dshost-plugin, last published 2026-11-13; the install command and the range come from its own manifest.

Install

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

dsh plugin --profile web add dshost-plugin

Compatibility

dshost-plugin ships no engines.dsh entry, so nothing checks it against your CLI version at boot. Read the npm page before installing.

If two plugins fight

Exposes the local web UI through a hosted relay. ds-harness-remote and dsh-mobile-plugin expose their own ingress; three ways in means three credentials to revoke when one leaks.

Who made it

Author: NoelJudeNoel. Repository: https://github.com/NoelJudeNoel/dshost-plugin. Package page: https://www.npmjs.com/package/dshost-plugin.

After install

It declares no dsh peer and renders a remote entry point in the profile a client connects to; after dsh plugin add dshost-plugin, dsh --profile web --dump-config lists the dshost-plugin row that mounts it.

Files it touches

No storage peer appears in the manifest of dshost-plugin, 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 dshost-plugin is the mirror command, dsh plugin --profile web remove dshost-plugin. 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 ds-harness-remote?

For dshost-plugin the recommendation is ds-harness-remote: It peers dsh-api-gateway and the settings pages, which keeps the exposure beside the thing being exposed.

What happens when dsh upgrades?

Nothing declares a version window for dshost-plugin: dsh --version tells you what you are running, and no check will tell you whether dshost-plugin matches it.