omdsh-dev/stent

Publishes the three Stent/Mixin packages that live inside the private deepseek-harness monorepo as one installable carrier, so the extension layer can be added through the normal plugin channel instead of a fork.

The repository is a decision record as much as a package: each non-obvious arrangement documents the concrete failure that forced it. It exists because the Stent/Mixin layer is three implementation packages inside a private monorepo that a consumer cannot install from the registry, so this workspace externalizes them behind one carrier. stent is a pure transformation service, stent-api a pure compatibility facade, and stent-dsh holds the DSH-facing facades, invariant and profile bootstrap; the loader installs hooks for the importing process and performs profile composition, dependency healing and argv normalization. The stated hard boundary is that the official @deepseek-ai/dsh-tool-cordis toolset stays an upstream dependency and is never republished here.

Development & Runtime ★ 18
View on GitHub ↗

Install

dsh plugin --profile web add @oh-my-dsh/stent-pack

The npm line from the README; @oh-my-dsh/stent-pack@0.1.1 resolves its registry repository to this repo. The root package is a carrier only: the workspace holds exactly three implementation packages (stent, stent-api, stent-dsh) and nothing else is republished.

Compatibility

Targets deepseek-harness snapshots 7b9644f2 (0812) and 9f9e2782a4 (0813). Activation happens at import time: the bin injects the compiled loader through NODE_OPTIONS=--import, so importing the loader is the activation boundary and a plain module import without it does nothing.

Details

Alternatives

idoall/dsh-update-status · iiwish/dsh-testkit · fuyue521/dsh-desktop-shortcut

More plugins in Development & Runtime

Browse more in Development & Runtime

Guides for Development & Runtime plugins