gh-setup-git-identity 0.8.0 → 0.8.2

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.
Files changed (44) hide show
  1. package/.github/workflows/release.yml +31 -0
  2. package/CHANGELOG.md +12 -0
  3. package/README.md +22 -8
  4. package/docs/case-studies/issue-32/README.md +162 -0
  5. package/docs/case-studies/issue-32/raw-logs/bun-add-command-stream-2.0.0-no-toolchain.txt +47 -0
  6. package/docs/case-studies/issue-32/raw-logs/bun-add-command-stream-2.4.0-no-toolchain.txt +10 -0
  7. package/docs/case-studies/issue-32/raw-logs/ci-run-37733836425-release-failed.txt +252 -0
  8. package/docs/case-studies/issue-32/raw-logs/command-stream-exit-codes.txt +4 -0
  9. package/docs/case-studies/issue-32/raw-logs/dry-run-fixed-publish-fails.txt +91 -0
  10. package/docs/case-studies/issue-32/raw-logs/dry-run-main-publish-fails.txt +81 -0
  11. package/docs/case-studies/issue-32/raw-logs/dry-run-rerun-after-fix.txt +195 -0
  12. package/docs/case-studies/issue-32/raw-logs/dry-run-rerun-before-fix.txt +198 -0
  13. package/docs/case-studies/issue-32/raw-logs/npm-registry-facts.txt +28 -0
  14. package/docs/case-studies/issue-32/raw-logs/setup-npm-fixed-node20.txt +8 -0
  15. package/docs/case-studies/issue-32/raw-logs/setup-npm-main-node20.txt +12 -0
  16. package/docs/case-studies/issue-34/README.md +53 -0
  17. package/docs/case-studies/issue-34/raw-logs/email-endpoint-headers.txt +5 -0
  18. package/docs/case-studies/issue-34/raw-logs/gh-2.102.0-scope-hint.txt +13 -0
  19. package/docs/case-studies/issue-34/raw-logs/gh-2.105.0-scope-hint.txt +13 -0
  20. package/docs/case-studies/issue-34/raw-logs/issue-report.txt +46 -0
  21. package/docs/case-studies/issue-34/raw-logs/prepared-pr-changeset-check.txt +3 -0
  22. package/docs/case-studies/issue-34/raw-logs/regression-after.txt +19 -0
  23. package/docs/case-studies/issue-34/raw-logs/regression-before.txt +22 -0
  24. package/experiments/issue-32-command-stream-exit-codes.mjs +27 -0
  25. package/experiments/issue-32-pinned-helpers.mjs +27 -0
  26. package/experiments/issue-32-release-dry-run.sh +66 -0
  27. package/experiments/issue-34-gh-scope-hint.mjs +68 -0
  28. package/package.json +1 -1
  29. package/scripts/changeset-version.mjs +8 -4
  30. package/scripts/create-github-release.mjs +8 -5
  31. package/scripts/create-manual-changeset.mjs +4 -5
  32. package/scripts/format-github-release.mjs +5 -5
  33. package/scripts/format-release-notes.mjs +5 -5
  34. package/scripts/instant-version-bump.mjs +8 -5
  35. package/scripts/publish-to-npm.mjs +18 -12
  36. package/scripts/release-deps.mjs +21 -0
  37. package/scripts/report-release-failure.mjs +143 -0
  38. package/scripts/setup-npm.mjs +80 -27
  39. package/scripts/version-and-commit.mjs +22 -5
  40. package/src/cli.js +43 -61
  41. package/src/index.js +88 -13
  42. package/test/cli.test.js +257 -0
  43. package/test/index.test.js +0 -17
  44. package/test/release-scripts.test.js +232 -0
@@ -278,3 +278,34 @@ jobs:
278
278
  2. Merge this PR to main
279
279
  3. The automated release workflow will create a version PR
280
280
  4. Merge the version PR to publish to npm and create a GitHub release
281
+
282
+ # Report a failed release on main - opens (or comments on) a GitHub issue,
283
+ # so that a merged change does not sit unpublished unnoticed (issue #32)
284
+ report-release-failure:
285
+ name: Report Release Failure
286
+ needs: [lint, test, release, instant-release]
287
+ if: >-
288
+ always() && github.ref == 'refs/heads/main' && (
289
+ needs.release.result == 'failure' || needs.release.result == 'cancelled' ||
290
+ needs.instant-release.result == 'failure' || needs.instant-release.result == 'cancelled' ||
291
+ (github.event_name == 'push' && (
292
+ needs.lint.result == 'failure' || needs.lint.result == 'cancelled' ||
293
+ needs.test.result == 'failure' || needs.test.result == 'cancelled'))
294
+ )
295
+ runs-on: ubuntu-latest
296
+ permissions:
297
+ contents: read
298
+ issues: write
299
+ steps:
300
+ - uses: actions/checkout@v4
301
+
302
+ - name: Setup Bun
303
+ uses: oven-sh/setup-bun@v2
304
+ with:
305
+ bun-version: latest
306
+
307
+ - name: Open or update the release failure issue
308
+ env:
309
+ GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
310
+ JOB_RESULTS: '{"lint":"${{ needs.lint.result }}","test":"${{ needs.test.result }}","release":"${{ needs.release.result }}","instant-release":"${{ needs.instant-release.result }}"}'
311
+ run: bun scripts/report-release-failure.mjs
package/CHANGELOG.md CHANGED
@@ -1,5 +1,17 @@
1
1
  # gh-setup-git-identity
2
2
 
3
+ ## 0.8.2
4
+
5
+ ### Patch Changes
6
+
7
+ - e740d67: Retry GitHub login once when the active account cannot read its primary email, then configure Git from the account selected during login. Honor `--repair`, `--no-auto-login`, and `--dry-run` during authentication recovery.
8
+
9
+ ## 0.8.1
10
+
11
+ ### Patch Changes
12
+
13
+ - 2c3fcc4: Read the CLI version from the installed package's package.json so --version stays correct across releases and working directories.
14
+
3
15
  ## 0.8.0
4
16
 
5
17
  ### Minor Changes
package/README.md CHANGED
@@ -33,7 +33,7 @@ gh-setup-git-identity
33
33
 
34
34
  - **Automatic identity setup**: Fetches username and email from GitHub
35
35
  - **Global and local configuration**: Configure git globally or per-repository
36
- - **Authentication check**: Prompts you to login if not authenticated
36
+ - **Authentication recovery**: Starts login when signed out or when the active credential lacks email access
37
37
  - **Git credential helper setup**: Automatically runs `gh auth setup-git` to configure git to use GitHub CLI for HTTPS authentication
38
38
  - **Dry-run mode**: Preview changes without making them
39
39
  - **Cross-platform**: Works on macOS, Linux, and Windows
@@ -94,14 +94,14 @@ Git Identity Options:
94
94
  --dry-run, --dry Dry run - show what would be done without making changes
95
95
  --verify Verify current git identity configuration
96
96
  --repair Repair git identity without triggering login (requires existing auth)
97
- --no-auto-login Disable automatic login if not authenticated
97
+ --no-auto-login Disable automatic login and re-login
98
98
  --verbose, -v Enable verbose output
99
99
 
100
100
  GitHub Authentication Options:
101
101
  --hostname GitHub hostname to authenticate with (default: github.com)
102
102
  --scopes, -s Authentication scopes, comma-separated (default: repo,workflow,user,read:org,gist)
103
103
  --git-protocol, -p Protocol for git operations: ssh or https (default: https)
104
- --web, -w Open a browser to authenticate (default: true)
104
+ --web, -w Open a browser to authenticate (default unless using --with-token)
105
105
  --with-token Read token from standard input
106
106
  --skip-ssh-key Skip generate/upload SSH key prompt
107
107
  --insecure-storage Save credentials in plain text instead of credential store
@@ -159,6 +159,14 @@ printf "y" | gh auth login -h github.com -s repo,workflow,user,read:org,gist --g
159
159
  gh auth setup-git -h github.com
160
160
  ```
161
161
 
162
+ ### When the Active Account Lacks Email Access
163
+
164
+ GitHub CLI can be signed in with a credential that cannot read the account's primary email. If `gh api user/emails` reports missing email access, the CLI starts `gh auth login` once and retries both identity lookups for the account you authorize. Recovery uses the configured hostname and login options. For OAuth login, it adds the reported email scope when your requested scopes omit both `user` and `user:email`.
165
+
166
+ If an environment token is active, replace it with a classic token that has `user:email` or `user`, or with a fine-grained user token that has **Email addresses: Read**. To use stored credentials or sign in with the browser, clear the environment token for the target host before rerunning the tool. [GitHub's email API permissions](https://docs.github.com/en/rest/users/emails#list-email-addresses-for-the-authenticated-user)
167
+
168
+ Use `--verbose` to see the authentication decision, login command and retry. The incident transcript, root cause and tests are in the [issue #34 case study](./docs/case-studies/issue-34/).
169
+
162
170
  ### Successful Run
163
171
 
164
172
  ```
@@ -226,18 +234,18 @@ This is useful when:
226
234
  - The `user.name` or `user.email` was accidentally cleared or corrupted
227
235
  - You want to reconfigure git identity without going through the login flow again
228
236
 
229
- The `--repair` option requires that you're already authenticated with GitHub CLI. If not authenticated, it will show helpful instructions for manual authentication.
237
+ The `--repair` option requires an existing GitHub CLI login with access to the primary email. It reports authentication or permission errors without starting login.
230
238
 
231
239
  ### Disabling Auto-Login
232
240
 
233
- By default, if you're not authenticated, the tool will automatically start the GitHub CLI login process. You can disable this behavior:
241
+ By default, the tool starts GitHub CLI login when signed out or when the active account lacks email access. You can disable automatic login:
234
242
 
235
243
  ```bash
236
- # Fail immediately if not authenticated (don't auto-login)
244
+ # Require a usable existing login
237
245
  gh-setup-git-identity --no-auto-login
238
246
  ```
239
247
 
240
- This is useful in scripts or automated environments where you want to fail fast rather than wait for an interactive login prompt.
248
+ Use `--dry-run` to preview identity changes with an existing login. It skips login and Git configuration writes.
241
249
 
242
250
  ## Library Usage
243
251
 
@@ -271,6 +279,8 @@ const result2 = await setupGitIdentity({
271
279
 
272
280
  Check if GitHub CLI is authenticated.
273
281
 
282
+ Pass `options.hostname` to check the active account on that host.
283
+
274
284
  **Returns:** `Promise<boolean>`
275
285
 
276
286
  #### `runGhAuthLogin(options?)`
@@ -326,6 +336,8 @@ Default authentication options object that can be imported and used as a referen
326
336
 
327
337
  Get GitHub user information (username and primary email).
328
338
 
339
+ Pass `options.hostname` to query a specific host.
340
+
329
341
  **Returns:** `Promise<{username: string, email: string}>`
330
342
 
331
343
  #### `setupGitIdentity(options?)`
@@ -334,6 +346,8 @@ Setup git identity based on GitHub user.
334
346
 
335
347
  **Parameters:**
336
348
  - `options.scope` - `'global'` or `'local'` (default: `'global'`)
349
+ - `options.hostname` - GitHub host for both identity lookups
350
+ - `options.authOptions` - Opt in to one re-login on an email permission error. Accepts `runGhAuthLogin` options and defaults the host to `github.com` when neither hostname option is set.
337
351
  - `options.dryRun` - Preview only, don't make changes (default: `false`)
338
352
  - `options.verbose` - Enable verbose logging (default: `false`)
339
353
  - `options.logger` - Custom logger (default: `console`)
@@ -403,7 +417,7 @@ For a detailed case study of this issue, see [docs/case-studies/issue-26/](./doc
403
417
 
404
418
  #### GitHub Authentication Options
405
419
 
406
- - `GH_AUTH_HOSTNAME` - GitHub hostname (default: `github.com`)
420
+ - `GH_AUTH_HOSTNAME` - GitHub hostname (defaults to `GH_HOST`, then `github.com`)
407
421
  - `GH_AUTH_SCOPES` - Authentication scopes (default: `repo,workflow,user,read:org,gist`)
408
422
  - `GH_AUTH_GIT_PROTOCOL` - Git protocol: `ssh` or `https` (default: `https`)
409
423
  - `GH_AUTH_WEB` - Open browser for authentication (default: `true`)
@@ -0,0 +1,162 @@
1
+ # Case Study: The `--version` fix was never published (Issue #32)
2
+
3
+ ## Summary
4
+
5
+ PR #31 fixed `gh-setup-git-identity --version` (it printed `0.1.0`) and was
6
+ merged on 2026-10-08. The post-merge **Checks and release** run on `main`
7
+ failed before it published anything. Nothing ran the release again, so npm
8
+ `latest` stayed on 0.8.0, which still prints `0.1.0`.
9
+
10
+ Investigation found one direct cause and three latent problems. Any of the
11
+ latent problems would have blocked or hidden the next release:
12
+
13
+ | # | Problem | Effect | Fix in this PR |
14
+ | --- | ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
15
+ | 1 | Release scripts load `command-stream@latest` through use-m. | command-stream 2.0.0 made `node-pty` a hard dependency. Its native build failed, so `setup-npm.mjs` crashed. | Pin use-m, command-stream and lino-arguments in `scripts/release-deps.mjs`. `setup-npm.mjs` loads no helpers. |
16
+ | 2 | `setup-npm.mjs` installs `npm@latest`. | npm 12 needs Node.js `^22.22.2 \|\| ^24.15.0 \|\| >=26`, and the job runs Node.js 20.20.2. A plain re-run today gets EBADENGINE. | Install `npm@11` and fail when npm stays below 11.5.1. |
17
+ | 3 | `await $` from command-stream **resolves** on a non-zero exit code. | The failed npm update exited 0. A failed `changeset publish` printed `Published …` and set `published=true`, which would create a GitHub release for a version that is not on npm. | `shell.errexit(true)` in every release-path script. |
18
+ | 4 | A re-run after a failed publish skipped the publish step. | The version commit on `main` already consumed the changesets. `version-and-commit.mjs` saw no changes and set neither `version_committed` nor `already_released`. | Report `already_released` when the rebase leaves no changesets. |
19
+ | 5 | Nothing reported the failed release on `main`. | The fix sat unpublished for two weeks, and downstream tools logged update failures ([hive-mind#3469](https://github.com/link-assistant/hive-mind/issues/3469)). | New `report-release-failure` job opens or updates a **Release on main failed** issue. |
20
+
21
+ ## Timeline
22
+
23
+ | Time (UTC) | Event |
24
+ | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
25
+ | 2026-01-16 11:31 | gh-setup-git-identity 0.8.0 is published. Its `--version` prints `0.1.0` (issue #30). |
26
+ | 2026-10-06 14:19 | command-stream 1.6.2 is published. |
27
+ | 2026-10-07 08:06 | command-stream 2.0.0 is published with `node-pty@^1.1.0` in `dependencies`. |
28
+ | 2026-10-08 05:43 | PR #31 is merged (3eb61a03). Run [37733836425](https://github.com/link-foundation/gh-setup-git-identity/actions/runs/37733836425) starts. |
29
+ | 2026-10-08 05:44:22 | `bun scripts/setup-npm.mjs` fails: `bun add -g command-stream-v-latest@npm:command-stream@latest` → `install script from "node-pty" exited with 1`. Nothing is versioned or published. |
30
+ | 2026-10-10 09:40 | [command-stream#218](https://github.com/link-foundation/command-stream/issues/218) is closed. |
31
+ | 2026-10-11 00:03 | command-stream 2.0.1 moves `node-pty` to `optionalDependencies`. |
32
+ | 2026-10-23 | Issue #32 is reported. npm `latest` is still 0.8.0. npm `latest` is now 12.2.1. |
33
+
34
+ ## Root cause 1: unpinned helpers
35
+
36
+ Every release script did:
37
+
38
+ ```js
39
+ const { use } = eval(
40
+ await (await fetch("https://unpkg.com/use-m/use.js")).text()
41
+ );
42
+ const { $ } = await use("command-stream");
43
+ ```
44
+
45
+ use-m resolves the bare name to `latest` and runs
46
+ `bun add -g command-stream-v-latest@npm:command-stream@latest`. On 2026-10-08,
47
+ `latest` was 2.0.0, with `node-pty` as a hard dependency. node-pty has no
48
+ linux-x64 prebuild, so Bun ran its `node-gyp` install script. That script
49
+ failed on the runner
50
+ ([raw log](raw-logs/ci-run-37733836425-release-failed.txt), lines 195–234).
51
+
52
+ Local reproduction without a C toolchain (only `bun`, `node`, `sh` on `PATH`):
53
+
54
+ - `bun add command-stream@2.0.0` exits 1 with
55
+ `error: install script from "node-pty" exited with 1`
56
+ ([log](raw-logs/bun-add-command-stream-2.0.0-no-toolchain.txt)).
57
+ - `bun add command-stream@2.4.0` exits 0
58
+ ([log](raw-logs/bun-add-command-stream-2.4.0-no-toolchain.txt)).
59
+
60
+ `setup-npm.mjs` only needed command-stream to run a single `npm install`
61
+ command. So it failed on a dependency it did not need.
62
+
63
+ ## Root cause 2: `npm@latest` moved to a major that needs Node.js 22
64
+
65
+ The issue suggested re-running the failed workflow as a workaround. That
66
+ would not work today. npm 12.2.1 is now `latest`, and it requires Node.js
67
+ `^22.22.2 || ^24.15.0 || >=26.0.0`. The release job uses
68
+ `actions/setup-node` with `20.x` (v20.20.2, npm 10.8.2 in run 37733836425).
69
+ Reproduced locally with the official Node.js v20.20.2 build:
70
+
71
+ ```text
72
+ $ npm install -g npm@latest
73
+ npm error code EBADENGINE
74
+ npm error notsup Not compatible with your version of node/npm: npm@12.2.1
75
+ npm error notsup Required: {"node":"^22.22.2 || ^24.15.0 || >=26.0.0"}
76
+ npm error notsup Actual: {"npm":"10.8.2","node":"v20.20.2"}
77
+ ```
78
+
79
+ The script from `main` then exited **0** and printed `Updated npm version: 10.8.2`
80
+ ([log](raw-logs/setup-npm-main-node20.txt)). The job would continue without
81
+ OIDC support (npm < 11.5.1) and fail later, at publish time. `npm install -g npm@11`
82
+ installs 11.21.1 on the same Node.js ([log](raw-logs/setup-npm-fixed-node20.txt)).
83
+
84
+ ## Root cause 3: command failures were reported as successes
85
+
86
+ `experiments/issue-32-command-stream-exit-codes.mjs`
87
+ ([output](raw-logs/command-stream-exit-codes.txt)):
88
+
89
+ ```text
90
+ shell.errexit available: function
91
+ default: resolved, code=3
92
+ errexit(true): rejected, code=3, Command failed with exit code 3
93
+ errexit(true) + .run({ capture: true }): rejected code=4
94
+ ```
95
+
96
+ The release scripts expect a failed command to throw, as in
97
+ `try { await $\`npm run changeset:publish\`; … } catch { retry }`. Without
98
+ errexit, the `catch`never runs.`experiments/issue-32-release-dry-run.sh`runs`version-and-commit.mjs`and`publish-to-npm.mjs`against a local bare
99
+ remote with`changeset:publish`replaced by`exit 1`:
100
+
101
+ - On `main` ([log](raw-logs/dry-run-main-publish-fails.txt)):
102
+ `Published gh-setup-git-identity@0.8.1 to npm`, exit 0,
103
+ `published=true`. The workflow would then create a GitHub release for an
104
+ unpublished version.
105
+ - With this PR ([log](raw-logs/dry-run-fixed-publish-fails.txt)): three
106
+ attempts, `Failed to publish after 3 attempts`, exit 1, no `published`.
107
+
108
+ ## Root cause 4: a re-run after a failed publish did not publish
109
+
110
+ The same script, run with `rerun` mode, re-runs the triggering commit after the
111
+ failed publish, as `gh run rerun --failed` would. The version commit `0.8.1` is
112
+ already on `main`, so `version-and-commit.mjs` rebases onto it, finds no
113
+ changesets, prints `No changes to commit`, and sets `version_committed=false`
114
+ with no `already_released`. The publish step is skipped
115
+ ([before](raw-logs/dry-run-rerun-before-fix.txt)). With this PR it prints
116
+ `Remote main already consumed the changesets (version 0.8.1).` and sets
117
+ `already_released=true`. The publish step runs and publishes
118
+ ([after](raw-logs/dry-run-rerun-after-fix.txt)).
119
+
120
+ ## Root cause 5: nobody was notified
121
+
122
+ A failed run on `main` only shows a red check on a merged commit. The new
123
+ `report-release-failure` job runs on `main` when `release` or `instant-release`
124
+ fails or is cancelled. On `push`, it also runs when `lint` or `test` fails or
125
+ is cancelled, because those failures skip the release. It runs
126
+ `scripts/report-release-failure.mjs`, which uses only `gh` and Node.js
127
+ built-ins. The report must still work when loading helpers is what broke. The
128
+ script opens a **Release on main failed** issue, or comments on the open one.
129
+ The report lists the run URL, the commit, the job results, and the
130
+ `gh run rerun <id> --failed` command.
131
+
132
+ ## Releasing the pending fix (0.8.1)
133
+
134
+ `.changeset/fix-cli-version.md` (patch) is still pending on `main`. Merging
135
+ this PR triggers **Checks and release** on `main` again. With the fixes above,
136
+ that run versions the package to 0.8.1, publishes it to npm, and creates the
137
+ GitHub release. `--version` then prints `0.8.1`.
138
+
139
+ This PR adds no second changeset. `scripts/validate-changeset.mjs` requires
140
+ exactly one changeset file in `.changeset/`, and the pending one already
141
+ produces the 0.8.1 patch release.
142
+
143
+ ## Verification
144
+
145
+ - `bun test`: `test/release-scripts.test.js` checks the pins, the
146
+ `setup-npm.mjs` logic (with a fake `npm`), errexit, the failure report (with
147
+ a fake `gh`), the workflow job, and the re-run path. All checks work
148
+ offline. Against the scripts on `main`, the pin and errexit checks fail.
149
+ - `experiments/issue-32-pinned-helpers.mjs` loads the pinned use-m,
150
+ command-stream and lino-arguments with Bun and exercises `$` and
151
+ `makeConfig`.
152
+ - `experiments/issue-32-release-dry-run.sh` gives the before/after dry runs
153
+ above.
154
+ - `actionlint` reports no new findings for `.github/workflows/release.yml`.
155
+ Its single finding (`github.head_ref` in an inline script) is already on `main`.
156
+
157
+ ## References
158
+
159
+ - Failed run: https://github.com/link-foundation/gh-setup-git-identity/actions/runs/37733836425
160
+ - command-stream node-pty regression: https://github.com/link-foundation/command-stream/issues/218
161
+ - npm trusted publishing (needs npm >= 11.5.1): https://docs.npmjs.com/trusted-publishers
162
+ - Downstream impact: https://github.com/link-assistant/hive-mind/issues/3469
@@ -0,0 +1,47 @@
1
+ bun add v1.4.3 (c6da4a4d3)
2
+ Resolving dependencies
3
+ Resolved, downloaded and extracted [259]
4
+ > Checking prebuilds...
5
+ > Rebuilding because directory /tmp/nopty/p2.0.0/node_modules/node-pty/prebuilds/linux-x64 does not exist
6
+
7
+ gyp info it worked if it ends with ok
8
+ gyp info using node-gyp@13.1.0
9
+ gyp info using node@26.12.0 | linux | x64
10
+ gyp ERR! find Python
11
+ gyp ERR! find Python --python was not set on the command line
12
+ gyp ERR! find Python Python is not set from environment variable PYTHON
13
+ gyp ERR! find Python checking if "python3" can be used
14
+ gyp ERR! find Python - executable path is ""
15
+ gyp ERR! find Python - "" could not be run
16
+ gyp ERR! find Python checking if "python" can be used
17
+ gyp ERR! find Python - executable path is ""
18
+ gyp ERR! find Python - "" could not be run
19
+ gyp ERR! find Python
20
+ gyp ERR! find Python **********************************************************
21
+ gyp ERR! find Python You need to install the latest version of Python.
22
+ gyp ERR! find Python Node-gyp should be able to find and use Python. If not,
23
+ gyp ERR! find Python you can try one of the following options:
24
+ gyp ERR! find Python - Use the switch --python="/path/to/pythonexecutable"
25
+ gyp ERR! find Python (accepted by both node-gyp and npm)
26
+ gyp ERR! find Python - Set the environment variable PYTHON
27
+ gyp ERR! find Python For more information consult the documentation at:
28
+ gyp ERR! find Python https://github.com/nodejs/node-gyp#installation
29
+ gyp ERR! find Python **********************************************************
30
+ gyp ERR! find Python
31
+ gyp ERR! configure error
32
+ gyp ERR! stack Error: Could not find any Python installation to use
33
+ gyp ERR! stack at PythonFinder.fail (/tmp/bunx-1001-node-gyp@latest/node_modules/node-gyp/lib/find-python.js:300:11)
34
+ gyp ERR! stack at PythonFinder.findPython (/tmp/bunx-1001-node-gyp@latest/node_modules/node-gyp/lib/find-python.js:160:17)
35
+ gyp ERR! stack at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
36
+ gyp ERR! stack at async configure (/tmp/bunx-1001-node-gyp@latest/node_modules/node-gyp/lib/configure.js:27:18)
37
+ gyp ERR! stack at async run (/tmp/bunx-1001-node-gyp@latest/node_modules/node-gyp/bin/node-gyp.js:81:18)
38
+ gyp ERR! System Linux 6.8.0-147-generic
39
+ gyp ERR! command "~/.nvm/versions/node/v26.12.0/bin/node" "/tmp/bunx-1001-node-gyp@latest/node_modules/.bin/node-gyp" "rebuild"
40
+ gyp ERR! cwd /tmp/nopty/p2.0.0/node_modules/node-pty
41
+ gyp ERR! node -v v26.12.0
42
+ gyp ERR! node-gyp -v v13.1.0
43
+ gyp ERR! $npm_package_name node-pty
44
+ gyp ERR! $npm_package_version 1.1.0
45
+ gyp ERR! not ok
46
+
47
+ error: install script from "node-pty" exited with 1
@@ -0,0 +1,10 @@
1
+ bun add v1.4.3 (c6da4a4d3)
2
+ Resolving dependencies
3
+ Resolved, downloaded and extracted [2]
4
+ Saved lockfile
5
+
6
+ installed command-stream@2.4.0 with binaries:
7
+ - $fy
8
+ - command-stream
9
+
10
+ 32 packages installed [592.00ms]