@ruoyang/dsh-plugin-deepseek-balance 1.0.0 → 1.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +14 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -43,6 +43,20 @@ In the Web UI: **Settings → Plugins**, then install by the package name above.
|
|
|
43
43
|
Through an agent session, the equivalent is the `plugin_manager` tool with
|
|
44
44
|
`action: install_bundle` and that package name as `target`.
|
|
45
45
|
|
|
46
|
+
### If you install through a registry mirror
|
|
47
|
+
|
|
48
|
+
`registry.npmmirror.com` and other read-only mirrors lag behind npmjs.org, and a package they have
|
|
49
|
+
not synced yet answers **404** — which looks exactly like "no such package". If your npm or pnpm is
|
|
50
|
+
pointed at a mirror (common on machines set up for fast installs), either wait for the sync or send
|
|
51
|
+
this scope to the official registry:
|
|
52
|
+
|
|
53
|
+
```sh
|
|
54
|
+
npm config set @ruoyang:registry https://registry.npmjs.org/
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
A scope key is a different setting from `registry`, so it also survives an inherited
|
|
58
|
+
`npm_config_registry` environment variable, which outranks every `.npmrc`.
|
|
59
|
+
|
|
46
60
|
A new bundle activates immediately; if the badge does not appear, reload the page once so the
|
|
47
61
|
browser picks up the new client module.
|
|
48
62
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@ruoyang/dsh-plugin-deepseek-balance",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.1",
|
|
4
4
|
"description": "Floating DeepSeek API balance badge for the DeepSeek Harness Web UI, backed by the harness's own DEEPSEEK_API_KEY credential",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "module",
|