Windows: Chromium bootstrap fails with exit 127 when bunx is missing, reported as a network problem
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- bun, playwright, typescript
- Domain
- devtools
Research direction
Start with the Chromium bootstrap in ./setup around line 2151, where the issue reports bunx playwright install chromium failing with exit 127. Check how the script invokes the installer and formats bootstrap errors; the issue suggests falling back to bun x or reporting a missing command. Done means setup can install Chromium when bunx is absent and identifies exit 127 as a missing command.
Written by the indexing model from the issue text.
Description
Summary
On Windows, ./setup reports the Chromium bootstrap as a network failure when the real cause is that bunx is not on PATH:
Installing Playwright Chromium...
./setup: line 2151: bunx: command not found
Chromium bootstrap: chromium-install — bunx playwright install chromium exited 127 (offline, proxy, or blocked download?)
Environment
- gstack 1.91.83.0 (5cb5e1c), Windows 11 10.0.26300, Git Bash
- Bun 1.4.3 installed with
winget install Oven-sh.Bun --scope user. The installer printed
Command line alias added: "bunx", but onlybun.exeexists in the package directory and nobunxshim was created.
Suggested fix
- Fall back to
bun x playwright install chromiumwhencommand -v bunxfails (or always usebun x). - When the exit code is 127, say the command is missing instead of suggesting offline/proxy causes.
Workaround
bun x playwright install chromium from the gstack checkout, then re-run ./setup.
- Dominant language
- TypeScript
- Stars
- 136k
- Forks
- 20.1k
- Avg merge
- 9h 45m
- Merged PRs (30d)
- 78
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from garrytan/gstack
-
bun run test leaves ship-measure-cli-* and sweep-cli-fake-* dirs in the real ~/.gstack/projects on every runPossibly taken @szsunyuan claimed this 1 day ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 70/100
garrytan/gstack#3091 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
garrytan/gstack#2847 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
priority:high
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
immich-app/immich#32426 ·
Maintainers usually reply within 1 day
-
documentation good first issue hacktoberfest help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
libredb/libredb-studio#1756 ·
Maintainers usually reply within 1 day
-
state:triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day