gigabuddy 0.2.0 → 0.3.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gigabuddy",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "The Gigabuddy CLI — sign in, and install @gigabuddy packages as yourself.",
   "type": "module",
   "license": "MIT",

package/src/lib/commands.d.ts

@@ -14,7 +14,23 @@ export declare function resolveEnv(options: {
     apiUrl?: string;
 }): Env;
 export declare function signIn(env: Env): Promise<UserCredentials>;
-export declare function loginCommand(env: Env): Promise<void>;
+/**
+ * `gigabuddy login` — sign in AND set npm up, because for this client they are
+ * one act. Installing `@gigabuddy` packages is what the CLI is for: nothing
+ * else on the machine reads the credential this writes (the agent client
+ * custodies its own), so a sign-in that stops short of npm has left the user
+ * with a file and no capability.
+ *
+ * There is no prompt, and deliberately so. The device flow cannot complete
+ * without a human approving a code in a browser, so "is anyone there?" is
+ * already answered yes by the time we get here — and TTY detection would get
+ * it wrong anyway for the SSH and devcontainer cases, silently skipping setup
+ * for someone who just approved. We tell them exactly what was written
+ * instead; `--no-npm` is there for the rare credential-file-only case.
+ */
+export declare function loginCommand(env: Env, options?: {
+    npm?: boolean;
+}): Promise<void>;
 /**
  * `gigabuddy login --npm` — make `npm install @gigabuddy/…` work as you.
  *