claudeup 6.2.1 → 6.3.0

package/README.md

@@ -62,8 +62,30 @@ claude [args...]            Check for plugin updates (1h cache), then run claude
 upgrade                     Update claudeup itself
 --version, -v               Version + update check
 --help, -h                  This list
+--theme light|dark          Force the palette. Otherwise: CLAUDEUP_THEME, then
+                            TERM_THEME, then a 250 ms terminal query, then
+                            COLORFGBG, then dark. Only the exact words
+                            "light"/"dark" count.
 ```
 
+### Light or dark
+
+claudeup decides once at startup, first answer wins: `--theme`, then the
+`CLAUDEUP_THEME` variable, then `TERM_THEME`, then a bounded (250 ms) wait for
+the terminal's OSC 10/11 reply — only when stdin and stdout are both TTYs — then
+`COLORFGBG`, then dark. A word that is not exactly `light` or `dark` (so `auto`,
+`Light`, an empty value) is no opinion and the next step runs; when the flag is
+given a bad word, that is an error naming both accepted values.
+
+`TERM_THEME` and `CLAUDEUP_THEME` are read from the process environment, never
+from a project's `.env`. Running from source needs `--no-env-file`, because Bun
+otherwise autoloads the cwd's `.env` before any code runs; the package scripts
+and the `bin/claudeup.js` source fallback already pass it, and the compiled
+binary never autoloads. The OSC 10/11 query itself is emitted by OpenTUI
+(0.1.107) when the renderer is created, regardless of the outcome; when an
+earlier step answered, claudeup never awaits or uses the reply, so first paint
+is not delayed and the terminal's answer has no influence.
+
 ### install vs update
 
 They differ in one thing: whether the pins are allowed to move.

package/bin/claudeup.js

@@ -50,7 +50,12 @@ if (binaryPath && !forceSource) {
 // 2. Fallback: run from source via Bun.
 const here = dirname(fileURLToPath(import.meta.url));
 const mainSrc = join(here, "..", "src", "main.tsx");
-const bunRun = spawnSync("bun", [mainSrc, ...args], { stdio: "inherit" });
+// --no-env-file: Bun autoloads the cwd's .env into process.env before any user
+// code runs, and the theme snapshot in main.tsx must precede any .env merge
+// (loadProjectDotenv is the only merger). The compiled binary never autoloads.
+const bunRun = spawnSync("bun", ["--no-env-file", mainSrc, ...args], {
+	stdio: "inherit",
+});
 if (bunRun.error) {
 	console.error(
 		`claudeup: no prebuilt binary for ${platform}-${arch}, and Bun is not installed.`,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claudeup",
-  "version": "6.2.1",
+  "version": "6.3.0",
   "description": "TUI tool for managing Claude Code plugins, MCPs, and configuration",
   "type": "module",
   "main": "src/main.tsx",
@@ -8,8 +8,8 @@
     "claudeup": "bin/claudeup.js"
   },
   "scripts": {
-    "start": "bun run src/main.tsx",
-    "dev": "bun --watch src/main.tsx",
+    "start": "bun --no-env-file src/main.tsx",
+    "dev": "bun --watch --no-env-file src/main.tsx",
     "typecheck": "tsc --noEmit",
     "lint": "biome check src/",
     "format": "biome format --write src/",
@@ -64,8 +64,8 @@
     "typescript": "^5.6.3"
   },
   "optionalDependencies": {
-    "claudeup-darwin-arm64": "6.2.1",
-    "claudeup-darwin-x64": "6.2.1",
-    "claudeup-linux-x64": "6.2.1"
+    "claudeup-darwin-arm64": "6.3.0",
+    "claudeup-darwin-x64": "6.3.0",
+    "claudeup-linux-x64": "6.3.0"
   }
 }