dsh-installed-plugins
A plugin catalog for DeepSeek Harness — stop wondering what all those plugins you installed actually do.
Installs a Plugin Catalog tab into the DSH settings page. It lists every third-party plugin in your profile with a plain-language description of what it does, its installed version, whether it is actually assembled, and whether a newer version exists on npm.
中文说明见文末 · Jump to Chinese
What you get
| 🗂 One list, everything explained | Every third-party plugin in your profile, with what it does and how to use it. |
| 🔄 Rebuilds itself | The host watches your profile's package.json. Install or remove a plugin and the catalog updates on its own — no command to run, no page reload. |
| 🆕 New-plugin marker | Anything that appeared since the last snapshot is badged and highlighted, so a fresh install never slips by unnoticed. |
| ⬆️ Update check | One click queries the npm registry and shows 1.7.25 → 1.7.29 plus an update available badge. Plugins installed from GitHub (github:owner/repo#<sha>) are compared against their upstream branch commit by commit. |
| 🛡 Compatibility verdict | Before anything is installed, each update is checked for real breakage: a raised peer requirement, a reverse constraint from another installed plugin, a Node engine mismatch. Verdicts are safe / has risk / incompatible — an incompatible one requires an explicit force. |
| 🚀 Update one, or all | Tick what you want and hit update selected, or use update all. Incompatible entries are never swept up silently. |
| 📜 Changelog in place | Every pending update can show its release notes, pulled from GitHub Releases or from the changelog file shipped in the package. A GitHub-source update shows the list of new commits instead. |
| ↩️ Backup + rollback | package.json and the lockfile are copied to backup-update-<timestamp>/ before anything changes, and restored automatically if the install fails. |
| 🗄 WebDAV backup & restore | Push the whole plugin setup — dependency specs, load order, local .mjs plugins, both patch layers, embedded local tarballs — to a WebDAV share as one JSON file, and rebuild it on another machine from the panel. |
| 🗑 Uninstall from the panel | Remove a plugin and everything that assembles it: the dependency, its dsh.profile.bundles entry, and any cordis.patch.yml row that loads it. You see the plan first. |
📄 PLUGINS.md |
The same data as a greppable, git-friendly Markdown file. Write it on demand from the panel. |
| 🔍 Search & filter | Instant client-side search over names, descriptions and tags. Zero round trips. |
| 📦 Zero dependencies | Plain JavaScript. No build step, no bundler, no transitive packages. |
Install
This package is not published to npm (the name dsh-plugin-catalog was already taken by an unrelated project, and dsh-installed-plugins is kept off the registry). Install it straight from this repository.
From the latest release tarball:
dsh plugin --profile web add https://github.com/Maxkun2333/dsh-plugin-catalog/releases/latest/download/dsh-installed-plugins.tgz
From a checkout (development):
git clone https://github.com/Maxkun2333/dsh-plugin-catalog.git
dsh plugin --profile web add link:./dsh-plugin-catalog
Then restart DSH. The tab appears under Settings → 插件目录.
Where descriptions come from
Three layers, highest priority first. You only ever have to write the top one.
| Layer | File | Who writes it |
|---|---|---|
| Your notes | data/plugins.json |
You. Never overwritten, and gitignored — it is yours. |
| Shipped descriptions | data/known-plugins.json |
This package. Covers ~20 popular community plugins so a fresh install is useful immediately. |
| npm fallback | the installed package's own description |
Nobody — read straight off the package. |
Copy data/plugins.example.json to data/plugins.json to start adding your own:
{
"entries": {
"dsh-pilot": {
"title": "Browser cockpit",
"what": "Drives a real Edge/Chrome over CDP so the agent can click and type on real pages.",
"use": "Use the pilot_* tools; a draggable cockpit panel shows live state.",
"repo": "https://github.com/guo6x/dsh-pilot",
"tags": ["browser", "automation"]
}
}
}
Configuration
Set in cordis.patch.yml (or wherever the plugin row lives):
- insert:
- id: plugin-catalog
name: 'dsh-installed-plugins'
config:
# profile: desktop # optional override; omitted = the running profile
# dataDir: ... # where plugins.json / catalog.json / PLUGINS.md live
# autoWrite: false # watch the profile but don't write files on change
profile is omitted on purpose. The plugin asks the running process (DSH_PROFILE_DIR, then DSH_PROFILE, then the profile directory the process itself was handed — the desktop client passes it as an argument and never sets those variables for itself) and only falls back to web when the harness was booted without a profile. Spelling a value out in the patch pins one profile for every install of the bundle — which is how a desktop client ended up listing the web profile's plugins, with the web profile's versions and update answers. Set it only when you deliberately want the panel to watch a different profile than the one you are running.
WebDAV credentials are not configured here — they live in the panel (and its settings.json), so they can be changed without editing this file or restarting DSH.
dataDir defaults — a link:/checkout install keeps everything inside the package. A package-manager install lands under node_modules, which may be pruned or relinked at any time, so user data moves to <DSH_HOME>/plugin-catalog instead.
Updating plugins
The updater changes exactly two things: the dependency spec in the profile's package.json, and whatever the package manager then does to node_modules. It never touches dsh.profile.bundles.
It checks compatibility first. Three failure modes are looked for, all of which have broken real DSH profiles:
- A raised peer requirement. The new version wants a newer peer than what is installed. (A real incident: a session backend began requiring a newer DSH core than the machine was running.)
- A reverse constraint. Another installed plugin pins a range the new version would no longer satisfy, so updating A would break B.
- A Node engine mismatch.
Two details worth knowing:
- Prerelease ranges are matched loosely. Strict semver would reject an installed
0.1.5-rc.2against^0.1.2-alpha.2— a range DSH plugins actually declare and work fine with. Judging strictly would flag nearly everything as incompatible. - A peer counts as satisfied if any reachable copy satisfies it. Core packages like
@deepseek-ai/dsh-credentialsexist twice — a possibly stale copy inside the profile and the one the running DSH install provides. The plugin asks Node the same question the host asks (a resolver anchored at the DSH entry script) instead of picking a path by hand. - Packages the host only bundles are judged by the kernel's version.
@deepseek-ai/dsh-client-ui-slots,-primitivesand-storeare shipped inside the client runtime, not as resolvable modules, so no copy of them exists in the running install. The whole@deepseek-ai/dsh*family is released in lockstep, so those peers are answered with the running kernel's version instead of whichever older copy happens to sit on the profile's walk-up path. Independently versioned packages (cordis,cosmokit,schemastery) are never inferred this way, and a kernel's version is only used for the profile that kernel is actually running.
Verdicts are advisory, never silently blocking: an incompatible entry still has a force update button, and every run leaves a rollback point.
A restart is required after updating. The running DSH process keeps the modules it already loaded; new versions take effect on next start.
GitHub-source plugins
A plugin installed as github:owner/repo#<sha> has no registry version, so the version check used to shrug at it: every such row read 需手动 / manual forever, even when the pinned commit was fifty commits behind upstream — which is exactly what happened with dsh-theme-endfield here, and why it kept looking up to date. Those rows are now compared against the repository's default branch.
| Source | What it answers | Cost |
|---|---|---|
GitHub compare API (/compare/<pin>...HEAD) |
direction (ahead / behind / diverged), the exact number of commits, the newest commit | 1 request, 60/hour per IP anonymously |
the commit Atom feed (github.com/<o>/<r>/commits.atom) |
the same head commit, plus the latest ~20 commits | no token, no API quota |
The Atom feed is not a nicety: the anonymous REST quota is per IP, so one shared NAT — or one other tool on the machine — can exhaust it, and the plugin then answers from the feed instead of reporting nothing. Results are cached per repository for a few minutes, and once a rate-limit answer is seen the REST source is skipped for a while rather than collecting 403s.
What the panel then shows and does:
- the card reads
1.0.1 → d551b261with the newest upstream commit as the reason, and 更新日志 opens the commit list instead of release notes; - the update button works: the profile's spec is rewritten to the new full sha and
pnpm installruns through the same backup → rewrite → install → rollback path an npm update uses; - the verdict is 有风险 / has risk — a commit bump carries no version number to reason about — or 不兼容 / incompatible when the target commit's own
package.jsondeclares a peer this machine does not satisfy. That manifest is fetched fromraw.githubusercontentat the target sha, so the DSH-core gate applies to commit updates exactly as it does to versions; - a pin that is ahead of the default branch, or has diverged from it, is left alone and says so; a branch or tag pin is reported as undecidable instead of being guessed at.
The plan guard was extended for this: a commit plan must carry a real sha, must stay a recognisable GitHub spec, and must still point at the same repository as the spec it replaces — a substituted owner/repo is refused outright.
GitHub Token (optional)
Anonymous GitHub API calls are capped at 60/hour per IP; a token raises that to 5000/hour and also reaches private repositories. Paste one into 代理设置 → GitHub Token (only public-repo read access is needed). It is stored in this plugin's settings.json — there is nowhere else a browser panel could keep it — and it is never sent back to the page: the panel only learns whether one is stored.
Watching an update run
pnpm install takes tens of seconds, and it retries a timed-out download on a 10-second then a 60-second backoff — so a normal install can sit silent for two minutes. The panel therefore shows a sticky progress card (it stays on screen while you scroll the list) with:
- the current phase — rewrite → backup → install → finish;
- an elapsed clock that ticks every second, so a static screen never means "frozen";
- the live tail of the install log, straight from pnpm;
- how long ago that log last moved, which is what separates "still downloading" from "actually stuck".
Proxy
Node and pnpm do not honour the system proxy. A machine can browse the web normally and still have an update fail with a download timeout — pnpm retries three times and then exits, which is why such a failure takes about two minutes.
The panel has a 代理设置 / Proxy row with three modes:
| Mode | Behaviour |
|---|---|
off |
pass nothing; the child inherits the environment as-is |
auto (default) |
detect at update time — environment variables first, then the OS setting (ProxyEnable / ProxyServer on Windows) |
manual |
use the URL you type, e.g. http://127.0.0.1:7897 |
Detection is deliberately re-run on every use rather than cached for the session: people start and stop their proxy mid-session. The panel shows both what it detected and what is currently in effect.
The proxy drives two things: the environment handed to the pnpm child, and — when undici happens to be resolvable — a per-request dispatcher for the plugin's own registry and changelog lookups. It is never installed globally, because a plugin silently rerouting all of DSH's network traffic would be a nasty surprise.
Backup and restore over WebDAV
A DSH profile cannot be reproduced on another machine from its dependency list. Three kinds of thing in it are machine-specific and silently lost by every "write down the npm names" approach:
file:dependencies — a local tarball that exists nowhere else;link:dependencies — a source checkout at an absolute path;- bare-file plugins under
<DSH_HOME>/plugins/*.mjs, plus theinsert:row in the home-levelcordis.patch.ymlthat loads them. They are in no registry at all.
So a backup is one self-describing JSON document:
| Field | What it carries |
|---|---|
profile.dependencies |
Every non-official dependency spec, verbatim. |
profile.bundles |
The dsh.profile.bundles order. It is append history, not alphabetical — order matters, so it is preserved rather than regenerated. |
unportable |
Each file:/link: dependency, with embedded when its payload travelled along, or a suggestion (github:owner/repo) derived from the local package's own repository field when it could not. |
assets |
file: payloads small enough to embed (base64 + sha256), e.g. a local plugin tarball. |
localPlugins |
The text of every <DSH_HOME>/plugins/*.mjs. |
patch |
Both cordis.patch.yml layers, as text. |
catalogNotes |
Your own data/plugins.json descriptions. |
howToRestore |
Instructions in plain language, so the file is still useful without this plugin. |
Backing up
Settings → 插件目录 → 🗄 WebDAV 备份, fill in the server, folder and credentials (Works with plain HTTP on a LAN, HTTPS anywhere else; Basic auth), then ⬆ 立即备份. The remote folder is created on demand, and older timestamped backups are pruned to the number you asked to keep.
Passwords are stored in plain text in the plugin's own settings.json, because there is nowhere else a browser panel could keep them — the panel says so, and the value is never sent back to the page (leave the field blank to keep it, or use 清除密码).
Restoring on another machine
Install DSH, install this plugin, restart, open the same panel, point it at the same WebDAV folder, 刷新列表, pick a backup and hit 恢复.
Nothing is written before you have seen the plan: what will be added, what will be upgraded, what cannot be ported and why, which files will be written, how the patch layers will be handled, and the exact lines package.json will gain.
It is a merge, not a reinstall. Plugins that are already there are never reinstalled:
| On the target machine | What restoring does |
|---|---|
| Not in the backup at all | Untouched — restoring never removes anything. |
| Same spec as the backup | Untouched, and not reinstalled. |
| Older version than the backup | Spec rewritten to the backup's; pnpm downloads just that package. |
| Newer version than the backup | Kept. Listed separately as 本机更高 — restoring brings a machine up to the backup, it does not roll one back. Tick 允许把本机更高的版本降回备份里的版本 to force it. |
@deepseek-ai/* (DSH itself) |
Never touched. |
Everything lands in one pnpm install at the end, which resolves against the existing lockfile: packages already satisfying their spec are not re-downloaded. If no dependency line changed, the install step is skipped entirely.
The details:
file:dependencies are rewritten to the local copy of the embedded payload, so a local tarball keeps working on a machine that never saw the original path (and stays put when the original path still holds the same bytes);link:dependencies that could not be embedded are skipped and reported (with agithub:substitute when the package knows its own repository) — never guessed;- local
.mjsplugins are written back, and a home-levelinsert:row is appended if the target does not already have that id; - an existing
cordis.patch.ymlon the target is never overwritten — the backup's copy is written beside it ascordis.patch.yml.restoredfor you to merge; - your own
data/plugins.jsonis written only if the target has none; package.jsonis edited by literal text substitution, so everything not deliberately changed stays byte-identical;package.json+ lockfile are snapshotted intobackup-restore-<timestamp>/, and rolled back ifpnpm installfails.
Restoring is a job, not a request, for the same reason updating is: it runs pnpm install and can take minutes. The progress card is sticky, counts the phases (download → plan → snapshot → files → manifest → install → done), and shows pnpm's live log tail.
A restart is required afterwards.
dsh.profile.bundlesis restored, but the running process has already loaded its modules.
Uninstalling a plugin
Every third-party card has a 卸载 button. It is the mirror image of installing, and the reason it needs a plan is that the same plugin can be assembled in three places:
| Where it lives | What uninstalling does |
|---|---|
dependencies in the profile's package.json |
The entry is deleted, and pnpm install prunes it from node_modules. |
dsh.profile.bundles |
The entry is removed, so the profile no longer loads it. |
a - insert: row in either cordis.patch.yml |
The row is disabled — a - id: <id> / disabled: true entry is appended, the same convention this ecosystem uses for retired plugins. |
That third one is the dangerous one, and it is why the panel will not uninstall blind: removing the package while a patch row still names it produces a profile that cannot boot (failed to apply loader entry include), and the panel that could undo it is the thing that will not start. The row is never deleted, so re-enabling it later is one line.
What the panel refuses, and says so up front:
- DSH's own packages (
@deepseek-ai/*) — they are the deployment, not plugins you installed; - this plugin itself — the uninstall runs from this panel;
- another plugin's dependency — the plan names who depends on it, so you remove the parent instead. (Otherwise the next install would put it straight back.)
What it tells you before you confirm: which dependency is removed, whether the load order changes, which patch rows get disabled, and which files stay on disk (link:/file: sources and bare-file .mjs plugins are never deleted — only their loading is).
Like updating, an uninstall is a job with the usual safety net: everything it touches is snapshotted into backup-uninstall-<timestamp>/ first, and rolled back if pnpm install fails.
A restart is required afterwards — the running process keeps the modules it already loaded.
HTTP API
The host half serves a small JSON API. Plugin-registered routes are not behind the SPA auth wall, so you can curl it:
| Method | Path | Purpose |
|---|---|---|
GET |
/dsh-installed-plugins/api/catalog |
The full catalog (plugins, counts, rev, lastError). |
POST |
/dsh-installed-plugins/api/refresh |
Rebuild and write catalog.json + PLUGINS.md. |
GET |
/dsh-installed-plugins/api/updates |
Latest versions plus a compatibility verdict and reasons per plugin. For a github: source the "latest" is the upstream commit (short sha) and the reasons carry the commit count and the newest commit message. |
POST |
/dsh-installed-plugins/api/update |
Start an update job. Body { "packages": ["a"], "force": false }, or {} for everything safe. Returns immediately. |
GET |
/dsh-installed-plugins/api/update/status |
Progress of the running (or last) job, including a log tail. |
GET |
/dsh-installed-plugins/api/changelog?pkg=<name> |
Release notes for that plugin's pending update — or, for a github: source, the list of new commits (source: github-commits). |
GET |
/dsh-installed-plugins/api/uninstall/plan?pkg=<name> |
What uninstalling that package would do — and why it is refused, if it is. Reads only. |
POST |
/dsh-installed-plugins/api/uninstall |
Start an uninstall job. Body { "pkg": "..." }. Returns immediately (started:false + blocked when it is not allowed). |
GET |
/dsh-installed-plugins/api/settings |
Proxy + WebDAV settings, whether a GitHub token is stored, and whether a WebDAV password is (no secret is included). |
POST |
/dsh-installed-plugins/api/backup/test |
Test the WebDAV connection. Body may carry a draft { "webdav": {...} }. |
POST |
/dsh-installed-plugins/api/backup/run |
Build a backup and PUT it. Returns the remote name, size and what was pruned. |
GET |
/dsh-installed-plugins/api/backup/list |
Every dsh-plugins-*.json in the remote folder, newest first. |
GET |
/dsh-installed-plugins/api/backup/preview?name=<file> |
Download a backup and return the restore plan — reads only, writes nothing. |
POST |
/dsh-installed-plugins/api/backup/restore |
Start a restore job. Body { "name": "..." }. Returns immediately. |
GET |
/dsh-installed-plugins/api/backup/status |
Progress of the running (or last) restore, including a log tail. |
POST |
/dsh-installed-plugins/api/backup/delete |
Delete one remote backup. Body { "name": "..." }. |
GET |
/dsh-installed-plugins/api/backup/file?name=<file> |
Download a backup straight through, for carrying it away by hand. |
Updating is a job, not a request: pnpm install takes tens of seconds, so the POST returns at once and the client polls the status endpoint.
Standalone CLI
The panel is built on the same code path as the CLI — there is exactly one implementation of the model (lib/catalog.mjs), so the file and the UI can never disagree.
node lib/catalog.mjs --profile web
# or
pwsh -File scripts/refresh.ps1
Development
npm run smoke # catalog model + slot client contract
scripts/smoke-slot-client.cjs is worth knowing about if you write DSH client plugins: it loads your client bundle with a fake window.__ModuleLoader__, runs apply() against a mock slots registry, and asserts the two contracts that silently produce a blank settings tab with nothing in the console:
- the component must be the second positional argument of
slots.register(options, component)— there is nocomponentkey in the options object; - it must be a real React component (the renderer does
jsx(entry.component, props)), not an object with arender()method.
Notes for DSH plugin authors
Learned while building this, in case they save you a debugging session:
- Theme tokens are
--dsw-alias-*/--dsw-specific-*, not--theme-*. A wrong prefix fails silently and every value falls back to your hard-coded default — which is how a search box ends up rendering black in a dark theme. QueryTheme.listTokensinstead of guessing. - Client bundles need no build step. The format is
window.__ModuleLoader__.load({ id, factory });factoryreceivesrequireand returnsmodule.exportswithapply/inject. React comes fromrequire('react'). - Never shell out to
dsh --profile … --dump-configfrom a plugin or script. It rewrites the profile'scordis.yml; under a file sandbox that fails withEPERM, anddsh-guardthen reports apreflight FAILthat looks like a corrupt config but is only a permission error. Derive state fromdsh.profile.bundlesandnode_modulesinstead.
License
MIT
中文说明
DSH 插件目录 —— 再也不用回忆「我装的那堆插件到底是干嘛的」。
在 DSH 设置页加一个「插件目录」页签,列出 profile 里所有第三方插件:用途说明、已装版本、是否真的装配了、npm 上有没有新版本。
装法
这个包没有发布到 npm(dsh-plugin-catalog 这个名字被一个无关项目先占了,dsh-installed-plugins 也就不上注册表了)。直接从本仓库安装:
dsh plugin --profile web add https://github.com/Maxkun2333/dsh-plugin-catalog/releases/latest/download/dsh-installed-plugins.tgz
重启 DSH,在 设置 → 插件目录 就能看到。
几个要点
- 装了插件会自动更新:host 侧用
fs.watch盯着 profile 的package.json,装 / 卸插件后目录自己重建,不用跑命令也不用刷新页面。 - 新装插件有标记:相对上次快照新增的插件会带 🆕 徽标并高亮。
- 更新插件:单个更新、勾选多个、或一键全部更新。每次更新前先做兼容性检查 —— 对比新版声明的 peer 要求、别的插件对它的反向依赖、Node 引擎要求,给出「可直接更新 / 有风险 / 不兼容」三级结论;标为不兼容的必须手动点「强制更新」才会执行。
- 更新前自动备份:
package.json与 lockfile 会复制到backup-update-<时间戳>/,安装失败会自动回滚。 - 更新日志:每个待更新的插件都能展开看它的 release notes(取 GitHub Releases,没有则取包内
CHANGELOG.md)。 - 说明分三层:你自己的笔记(
data/plugins.json,优先级最高、永不覆盖、已 gitignore)→ 包内置的社区插件说明(data/known-plugins.json,覆盖约 20 个常见插件)→ 包自带的 npm description 兜底。 PLUGINS.md:同一份数据的人读版,可 grep 可 git,面板上一键生成。- 待更新一眼可见:有新版本的插件按钮是橙色实心 + 呼吸光晕(不兼容的是红色,写着「⚠ 强制更新」),页签标题旁还有
⬆ 待更新 N徽标 —— 不用逐条扫列表。 - WebDAV 备份与还原:见下一节。
⚠️ 更新完需要重启 DSH:运行中的进程仍然用着已经加载进内存的旧模块,重启才会换成新版。
WebDAV 备份与还原(换电脑就靠它)
DSH 的 profile 没法只靠依赖名在另一台电脑上复现,有三类东西是跟机器绑死的、任何「抄一遍 npm 包名」的做法都会悄悄丢掉:
file:依赖 —— 一个只存在于本机的本地压缩包;link:依赖 —— 某个绝对路径下的源码目录;<DSH_HOME>/plugins/*.mjs这类裸文件插件(以及 home 层cordis.patch.yml里加载它的insert:行)—— 它们根本不在任何 registry 上。
所以备份是一份自描述的 JSON:非官方依赖的原样 spec、dsh.profile.bundles 的加载顺序(那是追加历史,不是字母序,必须原样带走)、本地裸文件插件正文、两层补丁文本、能内置的 file: 载荷(base64 + sha256)、你自己写的插件说明,外加一份给人看的 howToRestore 说明。
- 备份:设置 → 插件目录 → 🗄 WebDAV 备份 → 填服务器地址、远端目录、账号密码 → ⬆ 立即备份。目录不存在会自动创建,旧备份按你设定的份数自动清理。局域网可以走 http,公网请用 https。
- 还原:新机器上装好 DSH 和本插件 → 同一个面板填同一个地址 → 刷新列表 → 选一份 → 恢复。
- 先看预览再动手:会新增什么、升级什么、哪些搬不过来(以及为什么)、要写哪些文件、补丁层怎么处理、
package.json会多出哪几行 —— 全都先列出来。 - 是「合并」不是「重装」:备份里没有的插件不动(不删);已有且 spec 相同的一个都不重装;比备份旧的才会被改写;比备份新的默认保留(单列成「本机更高」,想强退得自己勾「允许降级」);官方
@deepseek-ai/*一律不碰。 - 只有一次安装:所有改动最后交给一条
pnpm install收口,按现有 lockfile 解析 —— 已经满足 spec 的包不会重新下载;如果一行依赖都没变,连这条命令都会跳过。 - 本地包不会丢:内置的
file:依赖会改写成新机器上落地后的路径,所以那个本地 tgz 在没见过的机器上照样能用;搬不过来的link:依赖会如实跳过并给出github:owner/repo替代建议,绝不瞎猜。 - 不覆盖目标机的配置:目标已有
cordis.patch.yml时不会覆盖,备份里那份写成cordis.patch.yml.restored让你自己合并;目标已有自己的data/plugins.json也保留不动。 - 失败自动回滚:改写
package.json前先快照到backup-restore-<时间戳>/,pnpm install失败就回滚。 - 密码是明文存的(在插件自己的
settings.json里)——浏览器面板没有别的地方可放,面板上写明了这一点,而且它不会回传给页面(留空 = 不改,另有「清除密码」)。
⚠️ 还原完同样要重启 DSH:加载顺序恢复了,但运行中的进程早就把模块读进内存了。
给 DSH 插件作者的三条经验
- 主题变量前缀是
--dsw-alias-*,不是--theme-*。写错会静默失败并全部落到兜底色 —— 搜索框在深色主题下发黑就是这么来的。用Theme.listTokens实查,别猜。 - 客户端产物不需要构建链:格式是
window.__ModuleLoader__.load({ id, factory }),React 用require('react')取。 - 不要在插件或脚本里调
dsh --profile … --dump-config:它会重写 profile 的cordis.yml,沙箱下EPERM,且dsh-guard会误报preflight FAIL(看起来像配置损坏,其实只是权限)。
许可证
MIT
No comments yet. Be the first to write one.