Skip to content

dsh-browser 0.3.1 — the bridge plugin and the extension

Choose a tag to compare

@DightEndless DightEndless released this 11 Oct 05:32
· 27 commits to main since this release

dsh-browser 0.3.1 — the bridge plugin and the extension

Two artifacts, same release:

  • dightendless-dsh-bridge-browser-0.3.1.tgz — the DSH plugin (bridge-browser),
    prebuilt, so no build step and no allowlisting are needed.
  • dsh-browser-extension-0.3.1.zip — the Chrome/Edge extension, already built.
    Unzip it, then load the folder through Load unpacked.
dsh plugin --profile web add https://github.com/DightEndless/dsh-browser/releases/download/v0.3.1/dightendless-dsh-bridge-browser-0.3.1.tgz

The plugin is also on npm — npm i @dightendless/dsh-bridge-browser — for setups that
resolve plugins from a registry rather than from a release asset.

What changed since 0.3.0

The package installs on a DSH 0.2.1-alpha host now. Every @deepseek-ai/dsh-* peer was
pinned to exactly 0.2.0-rc.2, so on a 0.2.1-alpha.1 host — the build the plugin
marketplace states it verifies against — the peer check failed before the plugin ever loaded.
The peers are now 0.2.0-rc.2 || >=0.2.1-alpha.1 <0.3.0, which makes both the rc line this
tree develops against and the alpha line it is verified against explicit. A broad
"minimum version" range would not have done it: npm does not let a prerelease satisfy a
range unless that range names a prerelease itself.

@deepseek-ai/dsh-invariants is an optional peer. It has no 0.2.1-alpha.* publication
at all (latest is 0.0.1-rc.1), and this package only imports its types: the companion
plugin carries inject: ['invariants'], so a host without that service never mounts it.

The READMEs name npm beside the release tarball, in both languages.

No extension behaviour changed in this release: the zip differs from 0.3.0 by its manifest
version alone.

Requirements

Chrome 116+ (or Edge); DSH 0.2.0-rc.2 or newer within 0.2.x — the published package's
peer ranges accept the 0.2.1-alpha line as well — and, for the installer route only,
Node.js 22+ with pnpm.

Removing the install-time blocker is not by itself proof that the plugin loads on a
0.2.1-alpha.1 host; that check belongs to the marketplace's own verification run, and its
result is recorded on the entry, not here.

Three ways to install

  1. Plugin from this release (one command, nothing to build) — the line above, or
    npm i @dightendless/dsh-bridge-browser.
  2. Extension only — download dsh-browser-extension-0.3.1.zip, unzip, then
    chrome://extensions → Load unpacked → pick the unzipped folder.
  3. Everything from source — the installer in the README clones the repository, builds
    both halves and registers the plugin bundle.

Then open the side panel on any page and ask: the model sees a numbered inventory of what is
on screen and acts through those numbers.