gigabuddy 0.4.1 → 0.5.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +20 -18
- package/bin/cli.js +11 -12
- package/index.js +4 -4
- package/package.json +1 -1
- package/src/lib/commands.d.ts +8 -13
package/README.md
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
# gigabuddy
|
|
2
2
|
|
|
3
3
|
Command-line sign-in for the [Gigabuddy](https://gigabuddy.com) platform.
|
|
4
|
-
Authenticates your machine and
|
|
4
|
+
Authenticates your machine, and can configure npm to install `@gigabuddy`
|
|
5
5
|
packages from the Gigabuddy registry.
|
|
6
6
|
|
|
7
7
|
## Install
|
|
@@ -16,7 +16,8 @@ npx gigabuddy login
|
|
|
16
16
|
|
|
17
17
|
```bash
|
|
18
18
|
gigabuddy setup # put Gigabuddy into Claude Code
|
|
19
|
-
gigabuddy login
|
|
19
|
+
gigabuddy login # sign in
|
|
20
|
+
gigabuddy login --npm # also set up npm for @gigabuddy packages
|
|
20
21
|
npm install @gigabuddy/app-kit
|
|
21
22
|
```
|
|
22
23
|
|
|
@@ -24,23 +25,24 @@ npm install @gigabuddy/app-kit
|
|
|
24
25
|
into Claude Code for you (it runs Claude Code's own `claude plugin` commands;
|
|
25
26
|
if `claude` isn't on your PATH it prints the `/plugin` commands to run
|
|
26
27
|
yourself). `login` opens your browser to sign in (device flow), stores your
|
|
27
|
-
credential
|
|
28
|
+
credential. Registry access is opt-in: `login --npm` configures `~/.npmrc`
|
|
29
|
+
for the `@gigabuddy` registry (and renews the credential when it expires).
|
|
28
30
|
|
|
29
31
|
## Commands
|
|
30
32
|
|
|
31
|
-
| Command | Description
|
|
32
|
-
| ------------------ |
|
|
33
|
-
| `setup` | Install the Gigabuddy plugin into Claude Code
|
|
34
|
-
| `login` | Sign in
|
|
35
|
-
| `login --npm` |
|
|
36
|
-
| `status` | Show the signed-in account
|
|
37
|
-
| `accounts` | List accounts on this machine and which is active here
|
|
38
|
-
| `use <name>` | Use an account for this repo (`--default`: machine-wide)
|
|
39
|
-
| `doctor [package]` | Diagnose sign-in, npm config, and registry access
|
|
40
|
-
| `logout` | Sign out (`--npm` removes only the npm credential)
|
|
41
|
-
|
|
42
|
-
**Options:** `--account <name>` acts as a specific account. `--
|
|
43
|
-
|
|
33
|
+
| Command | Description |
|
|
34
|
+
| ------------------ | -------------------------------------------------------- |
|
|
35
|
+
| `setup` | Install the Gigabuddy plugin into Claude Code |
|
|
36
|
+
| `login` | Sign in (never touches `~/.npmrc`) |
|
|
37
|
+
| `login --npm` | Also set up npm installs from the Gigabuddy registry |
|
|
38
|
+
| `status` | Show the signed-in account |
|
|
39
|
+
| `accounts` | List accounts on this machine and which is active here |
|
|
40
|
+
| `use <name>` | Use an account for this repo (`--default`: machine-wide) |
|
|
41
|
+
| `doctor [package]` | Diagnose sign-in, npm config, and registry access |
|
|
42
|
+
| `logout` | Sign out (`--npm` removes only the npm credential) |
|
|
43
|
+
|
|
44
|
+
**Options:** `--account <name>` acts as a specific account. `--staging`
|
|
45
|
+
targets the staging environment;
|
|
44
46
|
staging credentials are stored separately.
|
|
45
47
|
|
|
46
48
|
## Multiple accounts
|
|
@@ -59,14 +61,14 @@ Which account is active resolves as: the `GIGABUDDY_ACCOUNT` environment
|
|
|
59
61
|
variable, then the closest repo pin (set by `gigabuddy use`), then your
|
|
60
62
|
default account. Each account keeps its own credentials under `~/.gigabuddy`;
|
|
61
63
|
the npm credential in `~/.npmrc` is machine-wide and follows whichever
|
|
62
|
-
account ran `login` last.
|
|
64
|
+
account ran `login --npm` last.
|
|
63
65
|
|
|
64
66
|
## Credentials
|
|
65
67
|
|
|
66
68
|
`login` writes a refresh token to `~/.gigabuddy/user-credentials.json` (mode
|
|
67
69
|
0600). Short-lived platform tokens are minted from it on demand.
|
|
68
70
|
|
|
69
|
-
|
|
71
|
+
`login --npm` additionally adds two lines to `~/.npmrc` (0600), leaving the rest of the file
|
|
70
72
|
untouched:
|
|
71
73
|
|
|
72
74
|
```
|