WhatBrokeToday
GTA 6FAQ
Bun

Bun Source Codegen Prefers Older ~/.bun/bin/bun Over Running Binary

minor

Is it fixed? Not yet.

Ongoing since Nov 13, 17:45 UTC. First reported Nov 13, 17:45 UTC.

What happened

During source builds on upstream main, scripts/build/tools.ts:findBun() prioritizes the executable in ~/.bun/bin over process.execPath. This causes code generators to incorrectly use an older installed Bun version instead of the one currently running configure.

What caused it?

The findBun() function in scripts/build/tools.ts checks the executable in ~/.bun/bin before considering process.execPath during tool selection for source codegen.

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Official fix

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on GitHub issue

    Source codegen prefers an older ~/.bun/bin/bun over the Bun running configure

    Source

Evidence

1 report · 1 GitHubShow
  1. [1]
    GitHub First report
    Source codegen prefers an older ~/.bun/bin/bun over the Bun running configure(opens GitHub issue in a new tab)

    On upstream main d0f4fdd65fbd9548042aa5cd811a08f837ce4b4c, scripts/build/tools.ts:findBun() returns the executable in ~/.bun/bin before considering process.execPath, even when configure is already running under a newer explicitly selected Bun. During a normal debug source build on macOS arm64, I ran configure with Pantry's unchanged Bun 1.4.4 (38afee6c8) but the resulting tool selection chose the existing ~/.bun/bin/bun 1.4.2 for code generators. Neither installed executable was modified. This…

    by chrisbbreuer 0upvotes 2comments

FAQ

What happened in the Bun issue?

During source builds on upstream main, scripts/build/tools.ts:findBun() prioritizes the executable in ~/.bun/bin over process.execPath. This causes code generators to incorrectly use an older installed Bun version instead of the one currently running configure.

What is affected by the Bun issue?

Bun (versions: upstream main d0f4fdd65fbd9548042aa5cd811a08f837ce4b4c).

When did the Bun issue start and end?

It started Nov 13, 17:45 UTC and is still ongoing (5 d 10 h so far). This page updates as it develops.

How do I get alerts for Bun?

Subscribe to the Bun RSS feed for every new Bun incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Bun is down. Bun feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.