dsh-token-panorama 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 +18 -0
- package/README.zh-CN.md +17 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -62,6 +62,24 @@ After installation the sidebar shows a **Token Panorama** entry; selecting it op
|
|
|
62
62
|
|
|
63
63
|
To remove it, uninstall the `dsh-token-panorama` bundle from the Plugins page.
|
|
64
64
|
|
|
65
|
+
## npm package
|
|
66
|
+
|
|
67
|
+
The plugin is also published to the public npm registry as `dsh-token-panorama`. Storefronts
|
|
68
|
+
(the awesome-dsh-plugin catalog and the in-app market) can then install it by package name
|
|
69
|
+
and show a download figure, instead of falling back to the GitHub Release tarball.
|
|
70
|
+
|
|
71
|
+
- Publish a new version with `npm publish --access public`. npm requires either two-factor
|
|
72
|
+
authentication or a granular access token with Bypass 2FA enabled.
|
|
73
|
+
- The catalog reads the `name` field of the repository `package.json`, confirms that package on
|
|
74
|
+
the registry, and requires the npm package `repository` field to point back at this GitHub
|
|
75
|
+
repo. The mapping is discovered automatically; no field needs to be added to any listing.
|
|
76
|
+
- The download figure is the npm download count over a rolling 30-day UTC window
|
|
77
|
+
(`api.npmjs.org/downloads/point`), refreshed by the catalog nightly probe. It is not a
|
|
78
|
+
page-view or visit count: neither the catalog nor the market exposes any view metric.
|
|
79
|
+
GitHub Release asset downloads are a separate number and do not feed this field.
|
|
80
|
+
- Every change bumps `version` in `package.json`; publish that version too, so the registry
|
|
81
|
+
`latest` tag and the catalog `version` stay in step.
|
|
82
|
+
|
|
65
83
|
## Usage
|
|
66
84
|
|
|
67
85
|
1. Select **Token Panorama** in the sidebar.
|
package/README.zh-CN.md
CHANGED
|
@@ -53,6 +53,23 @@ plugin_manager install_bundle target="<本目录的绝对路径>"
|
|
|
53
53
|
|
|
54
54
|
卸载:在「插件」页面卸载 `dsh-token-panorama` 即可。
|
|
55
55
|
|
|
56
|
+
## npm 包与下载量口径
|
|
57
|
+
|
|
58
|
+
本插件同时发布到公共 npm registry,包名 `dsh-token-panorama`。目录站(awesome-dsh-plugin)与
|
|
59
|
+
应用内市场可据此按包名安装并显示下载量;未发布到 npm 时才回退到 GitHub Release 的 tgz 附件。
|
|
60
|
+
|
|
61
|
+
- 发布新版本:`npm publish --access public`。npm 要求开启两步验证,或使用勾选了 Bypass 2FA
|
|
62
|
+
的 granular access token。
|
|
63
|
+
- 目录站会读取仓库 `package.json` 的 `name`,在 registry 上确认同名包,并要求该 npm 包的
|
|
64
|
+
`repository` 字段回指本 GitHub 仓库。这层映射自动从 registry 抓取,条目里无需、也不允许
|
|
65
|
+
手写 `npm:` 字段。
|
|
66
|
+
- 市场显示的「下载量」是 npm 近 30 天(UTC 滚动窗口)下载数,来自
|
|
67
|
+
`api.npmjs.org/downloads/point`,由目录站每天夜间探测刷新。它不是「查看量 / 浏览量」:
|
|
68
|
+
目录与市场都不提供任何访问量字段。GitHub Release 附件的下载次数是另一套独立计数,
|
|
69
|
+
不会进入这个字段。
|
|
70
|
+
- 每次修改都会迭代 `package.json` 的 `version`,并发布新版本,使 registry 的 `latest`
|
|
71
|
+
与目录里的 `version` 保持一致。
|
|
72
|
+
|
|
56
73
|
## 使用
|
|
57
74
|
|
|
58
75
|
1. 在侧边栏点击 **Token 统计**。
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dsh-token-panorama",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.1",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "Token panorama for DSH: totals, cache hit rate, peak/off-peak cost, calendar heatmap, session tree, workspaces, CSV/JSON export, plus context clear/compact actions and prompt optimization.",
|
|
6
6
|
"keywords": [
|