@glaicer/supercode-token-usage-panel 1.0.1 → 1.2.0

package/README.md

@@ -13,7 +13,7 @@ Requires OpenCode v2 (`>=2.0.0`). On OpenCode v1 stay on `@glaicer/supercode-tok
 
 ## Install
 
-Install with the OpenCode CLI — it installs the package and registers the plugin in the global CLI configuration (`~/.config/opencode/cli.json`):
+Install with the OpenCode CLI — it installs the package and registers the plugin in the global server configuration (`~/.config/opencode/opencode.jsonc`):
 
 ```bash
 opencode plugin add @glaicer/supercode-token-usage-panel
@@ -24,7 +24,7 @@ Restart OpenCode after installing.
 > [!IMPORTANT]
 > **The first OpenCode load after installing this plugin may be slow.** That's OpenCode downloading the plugin's packages and managed tools into its cache — it happens once. Every subsequent start is fast.
 
-Manual install also works: add the package to the `plugins` array in `~/.config/opencode/cli.json`:
+Manual install also works: add the package to the `plugins` array in `~/.config/opencode/opencode.jsonc`:
 
 ```jsonc
 {
@@ -32,6 +32,22 @@ Manual install also works: add the package to the `plugins` array in `~/.config/
 }
 ```
 
+### Sidebar order
+
+The panel claims `after: "sidebar.content"`, and so do other plugins that extend the sidebar, so their relative order is the order in which they were registered. Entries in `opencode.jsonc` are always ordered before entries in `cli.json`, so register the panel here to place it relative to another sidebar plugin — for example, between `context-progress-bar` and `session-recap`:
+
+```jsonc
+{
+  "plugins": [
+    "@glaicer/supercode-context-progress-bar",
+    "@glaicer/supercode-token-usage-panel",
+    "@glaicer/supercode-session-recap"
+  ]
+}
+```
+
+The package ships a no-op server entry purely to make this possible: a `./tui`-only package can only be registered in `cli.json`, which always sorts last.
+
 ## Development
 
 ```bash

package/dist/index.js

@@ -0,0 +1,17 @@
+/**
+ * Server entrypoint (required so the plugin loads at all).
+ *
+ * The panel itself is TUI-only; all behaviour lives in `src/usage-panel.tsx`.
+ * This no-op server half exists for two host requirements: the server resolves
+ * a package through its main/server entry and only then reports `features.tui`,
+ * and sidebar claims from different plugins share one slot, so their relative
+ * order is the order of the `plugins` array that loaded them. Registering in
+ * `opencode.jsonc` is therefore the only way to place this panel relative to
+ * another `sidebar.content` claim such as session-recap — a `cli.json`-only
+ * entry is always ordered last.
+ */
+import { Plugin } from "@opencode/plugin";
+export default Plugin.define({
+  id: "supercode.token-usage",
+  setup() {}
+});

package/index.ts

@@ -0,0 +1,10 @@
+/**
+ * Root server entry for local-directory loading.
+ *
+ * When this package is referenced by directory path in `opencode.json(c)`
+ * `plugins`, the host loads `<dir>/index.{ts,js}` directly and does not consult
+ * `package.json` `exports`. The npm route keeps using `exports["."]` →
+ * `./dist/index.js`. Both entries define the same plugin; the host loads
+ * exactly one per package.
+ */
+export { default } from "./dist/index.js";

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "@glaicer/supercode-token-usage-panel",
-  "version": "1.0.1",
+  "version": "1.2.0",
   "description": "OpenCode TUI sidebar section: cumulative token usage and cost of the current session family.",
   "type": "module",
   "license": "MIT",
@@ -21,10 +21,14 @@
     "generation-speed"
   ],
   "exports": {
+    ".": "./dist/index.js",
+    "./server": "./dist/index.js",
     "./tui": "./dist/usage-panel.js"
   },
   "files": [
-    "dist"
+    "dist",
+    "index.ts",
+    "tui.js"
   ],
   "publishConfig": {
     "access": "public"

package/tui.js

@@ -0,0 +1,3 @@
+// Local-install entry: a directory plugin target resolves "<dir>/tui.*"
+// instead of package.json exports["./tui"]; npm installs use the export.
+export { default } from "./dist/usage-panel.js";