@rafay99/cvx 0.27.0 → 0.33.0

package/README.md

@@ -185,7 +185,7 @@ cvx completions zsh >> ~/.zshrc         # tab-complete commands + account names
 
 The vault is schema-versioned. The first time you run an interactive `cvx`
 command after updating from an older release, cvx shows a one-time prompt and,
-on confirmation, re-secures your tokens in the encrypted file vault (chmod 600)
+on confirmation, re-secures your tokens in the file vault (chmod 600)
 and upgrades the vault format. It's mandatory and runs once — you never see it
 again. The cd-hook and scripts keep working throughout; the prompt only appears
 in an interactive terminal. (Migration deliberately stays out of the OS keychain
@@ -212,6 +212,39 @@ man/cvx.1         man page (installed by Homebrew/npm → `man cvx`)
 First run of a bare `cvx` shows a welcome screen; `cvx welcome` shows it again,
 and `man cvx` opens the manual.
 
+## Testing
+
+```sh
+bun test          # full suite: parser + store units, and an e2e matrix that
+                  # drives every command against a throwaway CVX_HOME
+```
+
+The suite runs in ~2s, needs no setup, and never touches your real vault —
+CI (`.github/workflows/test.yml`) runs it on every PR. Three flows can't run
+headless and stay manual (use the sandbox below): real `cvx login` (browser),
+the interactive migration prompt (needs a PTY), and `cvx keychain enable`
+(the OS keychain is per-user).
+
+## Testing safely (sandbox)
+
+Never test a build against your real vault. Everything cvx touches — the vault,
+the global `~/.convex/config.json` it swaps, the rc files `hook --install`
+edits — resolves from one base directory, and setting `CVX_HOME` relocates all
+of it:
+
+```sh
+scripts/sandbox.sh                # build + drop into a shell with an EMPTY sandbox vault
+scripts/sandbox.sh --copy-vault   # same, but seeded with a COPY of your real vault
+```
+
+Inside that shell `cvx` is the fresh build and every command — `link`,
+`activate`, `rm`, even the migration prompt and `hook --install` — reads and
+writes only the sandbox. `exit` to leave; your real setup is never touched.
+Works without the script too: `CVX_HOME=/tmp/try cvx status`.
+
+One exception can't be sandboxed: the OS keychain is per-user, so skip
+`cvx keychain enable` in a sandbox (the default file backend is used anyway).
+
 ## Releasing
 
 Pushing to `main` (touching `bin/**` or `package.json`) triggers

package/{launcher.js → launcher.cjs}

@@ -28,4 +28,6 @@ if (res.error) {
   console.error(res.error.message);
   process.exit(1);
 }
+// Propagate a signal death (Ctrl-C etc.) as a signal, not a generic failure.
+if (res.signal) process.kill(process.pid, res.signal);
 process.exit(res.status === null ? 1 : res.status);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rafay99/cvx",
-  "version": "0.27.0",
+  "version": "0.33.0",
   "description": "Switch Convex accounts per project automatically — run many Convex accounts across projects at once, no login/logout churn, no deploy keys, no tokens in your repos",
   "keywords": [
     "convex", "convex-dev", "convex-cli", "cli", "command-line",
@@ -14,15 +14,15 @@
   "bugs": "https://github.com/rafay99-epic/convex-switch/issues",
   "repository": { "type": "git", "url": "git+https://github.com/rafay99-epic/convex-switch.git" },
   "author": "Abdul Rafay",
-  "bin": { "cvx": "launcher.js" },
+  "bin": { "cvx": "launcher.cjs" },
   "man": ["cvx.1"],
-  "files": ["launcher.js", "cvx.1", "README.md", "LICENSE"],
+  "files": ["launcher.cjs", "cvx.1", "README.md", "LICENSE"],
   "engines": { "node": ">=16" },
   "optionalDependencies": {
-    "@rafay99/cvx-darwin-arm64": "0.27.0",
-    "@rafay99/cvx-darwin-x64": "0.27.0",
-    "@rafay99/cvx-linux-x64": "0.27.0",
-    "@rafay99/cvx-linux-arm64": "0.27.0",
-    "@rafay99/cvx-win32-x64": "0.27.0"
+    "@rafay99/cvx-darwin-arm64": "0.33.0",
+    "@rafay99/cvx-darwin-x64": "0.33.0",
+    "@rafay99/cvx-linux-x64": "0.33.0",
+    "@rafay99/cvx-linux-arm64": "0.33.0",
+    "@rafay99/cvx-win32-x64": "0.33.0"
   }
 }