gigabuddy 0.2.0 → 0.3.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 +15 -12
- package/bin/cli.js +63 -14716
- package/index.js +55 -14647
- package/package.json +1 -1
- package/src/lib/commands.d.ts +17 -1
package/README.md
CHANGED
|
@@ -3,23 +3,25 @@
|
|
|
3
3
|
The Gigabuddy CLI. Sign in, and install `@gigabuddy` packages as yourself.
|
|
4
4
|
|
|
5
5
|
```bash
|
|
6
|
-
npm install -g gigabuddy # or: npx gigabuddy login
|
|
6
|
+
npm install -g gigabuddy # or just: npx gigabuddy login
|
|
7
7
|
|
|
8
|
-
gigabuddy login
|
|
8
|
+
gigabuddy login
|
|
9
9
|
npm install @gigabuddy/app-kit
|
|
10
10
|
```
|
|
11
11
|
|
|
12
|
-
That's the whole onboarding
|
|
13
|
-
|
|
12
|
+
That's the whole onboarding — one command. Signing in also sets `npm` up,
|
|
13
|
+
because installing `@gigabuddy` packages is what the credential is for.
|
|
14
14
|
|
|
15
15
|
## Commands
|
|
16
16
|
|
|
17
|
-
| Command | What it does
|
|
18
|
-
| ----------------------- |
|
|
19
|
-
| `gigabuddy login` | Sign in (device flow — opens your browser)
|
|
20
|
-
| `gigabuddy login --npm` |
|
|
21
|
-
| `gigabuddy status` | Who you're signed in as
|
|
22
|
-
| `gigabuddy logout` | Sign out (`--npm` clears only the npm credential)
|
|
17
|
+
| Command | What it does |
|
|
18
|
+
| ----------------------- | ---------------------------------------------------------------- |
|
|
19
|
+
| `gigabuddy login` | Sign in (device flow — opens your browser) and set up `~/.npmrc` |
|
|
20
|
+
| `gigabuddy login --npm` | Re-mint just the npm credential, when it expires |
|
|
21
|
+
| `gigabuddy status` | Who you're signed in as |
|
|
22
|
+
| `gigabuddy logout` | Sign out (`--npm` clears only the npm credential) |
|
|
23
|
+
|
|
24
|
+
Pass `--no-npm` to sign in without touching `~/.npmrc`.
|
|
23
25
|
|
|
24
26
|
`--staging` targets the staging environment; its credentials are stored
|
|
25
27
|
separately, so a staging login never becomes your production one.
|
|
@@ -32,7 +34,7 @@ session behind it is deliberately narrow — it identifies you, lets you see wha
|
|
|
32
34
|
you can reach, install from the Gigabuddy registry, and run agents you sponsor;
|
|
33
35
|
it is not your full account authority.
|
|
34
36
|
|
|
35
|
-
`login
|
|
37
|
+
`login` also adds two lines to `~/.npmrc` (0600), leaving everything else in
|
|
36
38
|
that file exactly where it was:
|
|
37
39
|
|
|
38
40
|
```
|
|
@@ -45,7 +47,8 @@ nothing else on the platform — because `.npmrc` is a file that ends up in CI
|
|
|
45
47
|
logs and is readable by every postinstall script that runs on your machine. It
|
|
46
48
|
lives 30 days (npm has nowhere to put a token refresh), and it dies with your
|
|
47
49
|
session: signing out, or an admin revoking the session, stops installs within
|
|
48
|
-
about a minute. Re-run `gigabuddy login --npm` to get a fresh one
|
|
50
|
+
about a minute. Re-run `gigabuddy login --npm` to get a fresh one without
|
|
51
|
+
another browser round-trip.
|
|
49
52
|
|
|
50
53
|
Which packages you can install is decided per install, against your own access —
|
|
51
54
|
the credential only proves who you are.
|