dsh-plugin-template

项目详情摘要

dsh-plugin-template English | 中文 A complete dual-side DeepSeek Harness plugin template. It demonstrates the full plugin surface — a **host** plugin exposing a Typert Remote, and a **client** plugin mounting that Remote into a React view — with type-checking, linting, unit tests, CI, and publishing metadata wired up. Out of the box it registers a `greet` Remote: the host composes `"Hello, "` from a configurable prefix, and the client renders the result in a new "Greet" tab. Structure `package.json` is the only manifest Harness needs. `dsh.bundle.patch` makes the package an installable profile bundle; `dsh.client` declares the Web client bundle and the client packages it injects. The host entry is the ordinary Cordis `name`/`apply` export; the client entry is bundled to `lib/client.js` and loaded by the Web harness module loader. Requirements Node.js `>= 22.19` (or `>= 24`) pnpm `>= 9` DeepSeek Harness `>=0.1.0-rc.6` Install from a local checkout Restart the Web Harness after rebuilding the plugin. A "Greet" tab appears in the session view ring showing `Hello, DSH`. Remove it with: Install from Git A Git install fetches sources, not built artifacts, so pnpm runs the `prepare` script to build `lib/`. pnpm ≥10 blocks that build until you allow it; on the first failed `add`, `dsh` prints the fix — copy the package key it shows into the profile's `pnpm-workspace.yaml`: then re-run the `add`. That allowance lets the package run code at install time, so only allow packages you trust (and pin a commit). Development `check` runs `typecheck`, `lint`, `test`, and `build`. CI runs the same command after `pnpm install --frozen-lockfile`. Individual scripts: Renaming the package Keep these values in sync when you rename: `package.json` → `name`, `exports`, `files` `build.mjs` → the `_