cf 0.0.6 → 0.2.0

package/README.md

@@ -18,7 +18,7 @@ Requires Node.js 22 or newer.
 cf auth login        # Authenticate with Cloudflare
 cf --help            # Browse all commands
 cf <command> --help  # Per-command help
-cf complete bash     # Install shell completions
+cf complete bash >> ~/.bashrc   # Install shell completions
 ```
 
 ## Authentication
@@ -26,9 +26,7 @@ cf complete bash     # Install shell completions
 cf resolves credentials in this order:
 
 1. `CLOUDFLARE_API_TOKEN` environment variable
-2. Stored API token (via `cf auth login --token <token>`)
-3. cf OAuth token (via `cf auth login`)
-4. Wrangler OAuth token (falls back automatically)
+2. cf OAuth token (via `cf auth login`; refreshed automatically)
 
 ## Output
 

package/bin/cf

@@ -30,6 +30,17 @@ process.on("warning", (warning) => {
 	console.error(warning.stack ?? `${warning.name}: ${warning.message}`);
 });
 
+// Wrangler-2-style local-install delegation, handled HERE — before the
+// main bundle is imported — so that when cf hands off to a project-local
+// copy, the global install never pays to load its (large) command tree.
+// The delegation logic lives in src/lib/delegate.ts and is emitted as a
+// small standalone chunk (see tsdown.config.ts `entry.delegate`).
+const { maybeDelegateFromProcess } = await import("../dist/delegate.mjs");
+const delegation = await maybeDelegateFromProcess();
+if (delegation.delegated) {
+	process.exit(delegation.exitCode ?? 0);
+}
+
 // Dynamic so the version check above runs first — static imports are
 // hoisted ahead of all user code, which means a too-old Node would fail
 // resolving the bundle before we get a chance to print a friendly error.