@promptctl/cc-candybar 1.22.0 → 1.23.0

package/README.md

@@ -18,19 +18,19 @@ CCCandybar is a statusline renderer for [Claude Code](https://docs.anthropic.com
 
 A background daemon caches git state, usage data, and per-session values across concurrent Claude Code sessions. The renderer connects to the daemon over a Unix socket, so every invocation is fast (~50ms budget) and stateful.
 
-## Quick start (macOS)
+## Quick start
 
 ```bash
 pnpm dlx @promptctl/cc-candybar@latest install
 ```
 
-That single command:
+That single command (re-run it any time to update to the latest release):
 
-1. Builds `~/Applications/CCCandybarURLHandler.app` and registers the `cc-candybar://` URL scheme with macOS Launch Services.
-2. Copies the runtime into `~/Library/Application Support/CCCandybar/url-handler.mjs` (stable path independent of pnpm cache).
-3. Writes the statusline renderer command into `~/.claude/settings.json`.
+1. Stages the runtime at a stable path independent of any package-manager cache — `~/Library/Application Support/CCCandybar/` on macOS, `$XDG_DATA_HOME/cc-candybar/` on Linux — as `bin/cc-candybar` (the prebuilt native render binary for your platform, or a node entry where none exists) beside `dist/index.mjs` (the daemon + CLI bundle).
+2. On macOS, builds `~/Applications/CCCandybarURLHandler.app` and registers the `cc-candybar://` URL scheme with Launch Services.
+3. Writes the staged `bin/cc-candybar` path as the statusline command into `~/.claude/settings.json` (skipped with a notice if you've customized the command; `--force` overwrites).
 
-Restart Claude Code. The statusline appears with the bundled default layout (directory, git, model, session, today, context). Cmd-clicking clickable cells fires `cc-candybar://` URL verbs that the daemon dispatches.
+Restart Claude Code. The statusline appears with the bundled default layout — an identity row (directory, gitaculous, toolbar) over a status row (model, context, cacheTimer, block, weekly). On macOS, Cmd-clicking clickable cells fires `cc-candybar://` URL verbs that the daemon dispatches (via the URL handler registered in step 2).
 
 ## Customization
 
@@ -117,21 +117,25 @@ The DSL config picks a base palette via `globals.palette` (e.g. `textual-dark`,
 
 ## Installation
 
-Requires Node.js 18+, Claude Code, and Git 2.0+. For best display, install a [Nerd Font](https://www.nerdfonts.com/) so the powerline glyphs render correctly.
+Requires Node.js 20.19+ (within the 20.x line) or 22.12+, Claude Code, and Git 2.0+. For best display, install a [Nerd Font](https://www.nerdfonts.com/) so the powerline glyphs render correctly.
 
 ### Manual setup
 
-Edit `~/.claude/settings.json` directly. Pin the version — don't use `@latest` (pnpm caches aggressively and won't pick up new releases).
+Run the install once to stage the runtime, then point `~/.claude/settings.json` at the staged entry (this is also exactly what `install` writes):
 
 ```json
 {
   "statusLine": {
     "type": "command",
-    "command": "pnpm dlx @promptctl/cc-candybar@0.2.3"
+    "command": "'/Users/you/Library/Application Support/CCCandybar/bin/cc-candybar'"
   }
 }
 ```
 
+### Developing against a checkout
+
+`just deploy` builds `dist/index.mjs` and stages the native binary at `bin/cc-candybar-native` — point your statusline command at that path. On a machine without cargo, `pnpm install && pnpm build` builds only the bundle — point your statusline at the committed `bin/cc-candybar` node entry instead. Either way the bar renders HEAD; the daemon watches the built bundle and respawns itself on rebuild.
+
 ### Config file
 
 Customization lives in `.cc-candybar.json5`. See the [Customization](#customization) section above for the resolution order. Saved edits hot-reload — no restart needed.

package/bin/cc-candybar

@@ -1,6 +1,18 @@
-#!/bin/sh
-echo "cc-candybar: native binary not installed." >&2
-echo "Postinstall did not stage a platform binary. Reinstall on darwin-arm64," >&2
-echo "darwin-x64, linux-x64, or linux-arm64; or open an issue at" >&2
-echo "https://github.com/promptctl/cc-candybar/issues." >&2
-exit 1
+#!/usr/bin/env node
+// The package's one committed entry point. Dynamic import is deliberate: this
+// same file runs from two homes with two module systems — inside the npm
+// package (nearest package.json says type:module, so the extensionless entry
+// runs as ESM) and staged at the support dir with no package.json above it
+// (so it runs as CommonJS) — and import() is the one construct that reaches
+// the ESM bundle from either, resolving relative to this file no matter the cwd.
+// [LAW:composability] No install scripts, no staging ritual — this works the
+// moment any package manager lays the tarball on disk. The native fast-path
+// binary is a deploy-time optimization staged by `cc-candybar install`
+// (published) or `just install-rust` (source checkout, bin/cc-candybar-native).
+import("../dist/index.mjs").catch((err) => {
+  console.error(
+    "cc-candybar: failed to load dist/index.mjs — " +
+      (err && err.message ? err.message : String(err)),
+  );
+  process.exit(1);
+});