Possible Bun 1.4.1 Android/Bionic compile regression with splitting:true #42837

Activity

1. robobun commented on Sep 16, 2026

   

   robobun

   on Sep 16, 2026

   Collaborator

   More actions

   I tried to reproduce this with the stock OpenCode 1.18.31 source and Bun 1.4.1 on Linux x64. I do not have an Android device, so I could not run a bun-linux-aarch64-android executable.

   Bun version: 1.4.1 (release build from GitHub) on linux x64

   Attempt 1: Build OpenCode 1.18.31 with its own build script. The script uses minify: true, splitting: true and compile (see packages/opencode/script/build.ts). Then start the compiled executable and call the agent and config routes.

   $ git clone --depth 1 --branch v1.18.31 https://github.com/anomalyco/opencode.git
   $ cd opencode && bun install
   $ cd packages/opencode
   $ bun run script/build.ts --single --skip-embed-web-ui --skip-install
   Loaded models.dev snapshot
   building opencode-linux-x64
   Running smoke test: dist/opencode-linux-x64/bin/opencode --version
   Smoke test passed: 0.0.0--202609160107
   
   $ dist/opencode-linux-x64/bin/opencode serve --port 14141 --hostname 127.0.0.1 &
   opencode server listening on http://127.0.0.1:14141
   
   $ curl -s -w "\nHTTP %{http_code}\n" http://127.0.0.1:14141/global/health
   {"healthy":true,"version":"0.0.0--202609160107"}
   HTTP 200
   
   $ curl -s -w "\nHTTP %{http_code}\n" http://127.0.0.1:14141/config
   {"$schema":"https://opencode.ai/config.json","command":{},"plugin":[],"username":"unknown","mode":{},"agent":{}}
   HTTP 200
   
   $ curl -s -w "\nHTTP %{http_code}\n" http://127.0.0.1:14141/agent
   [{"name":"build","description":"The default agent. Executes tools based on configured permissions.","mode":"primary","native":true,"permission":[...]}, ...]
   HTTP 200

   Expected HTTP 500 with TypeError: undefined is not an object (evaluating 'a.name'). Got HTTP 200 on all routes.

   Attempt 2: Search the OpenCode 1.18.31 source for the routes in the report.

   $ grep -rn '/api/agent\|/api/reference\|"/reference"' packages/opencode/src
   (no matches)

   The stock source has no /api/reference or /api/agent route. The tree that fails is a modified one (@androidtui/core is a fork of @opentui/core).

   Conclusion: The stock OpenCode 1.18.31 build with Bun 1.4.1, splitting: true and compile works on Linux x64. I cannot tell from the report alone whether the failure comes from the Android runtime, from the modified source tree, or from a bundler change between 1.4.0 and 1.4.1.

   To make progress, please provide:

   1. The exact Bun.build options and the changes to the source tree (the /api/* routes, the @androidtui/core swap, the target value).
   2. The full stack trace of the TypeError. Build with minify: false and sourcemap: "linked" (or "inline") so the trace has file names and the real variable name, not a.
   3. A check of the same build with --target=bun-linux-x64 (or your host target) on a Linux machine. If it fails there too, the Android runtime is not the cause.
   4. If possible, a small standalone reproducer. The module that throws at a.name, its importers, and whether that module is reached through import() would already narrow this a lot. Several import() and require() interop changes landed in 1.4.1 (for example bundler: tree-shake unobserved exports of import() / require() targets #32557, bundler: give a split import() of a lifted CommonJS module its namespace as default #41231, bundler: wrap a split import() with __toESM when the target is CommonJS at link time #41237, bundler: read .default of a split require() whose target is CommonJS at link time #41243), so a reduced case around the failing dynamic import is the most useful thing.
2. bd-loser

   added a commit that references this issue on Sep 17, 2026

   fix(build): disable bun splitting; pin bun-termux 1.4.2-patched; open…

   ...

   d936e12
3. martinstiago commented on Sep 18, 2026

   

   martinstiago

   on Sep 18, 2026

   More actions

   Confirming this reproduces on stock opencode on macOS (darwin-arm64) — it's not Android/Bionic- or fork-specific.

   (Context: this also blocks anomalyco/opencode#44946, which bumps opencode's embedded Bun to 1.4.x — see the "Blocker" note there. Posting here since the root cause lives in Bun's bundler.)

   Setup: unmodified anomalyco/opencode dev (Sep 18, b02acc1), only change is packageManager: [email protected]. Built with its own build script (packages/opencode/script/build.ts: Bun.build + compile, minify: true, splitting: true).

   Matrix:

   Configuration	Result
   Bun 1.3.14, compiled binary (stock v1.18.31 release)	PASS — full agent turn works
   Bun 1.4.1, compiled binary, splitting: true	FAIL — first agent turn crashes
   Bun 1.4.2, compiled binary, splitting: true	FAIL — same crash
   Bun 1.4.2, compiled binary, splitting: false	PASS — full agent turn works
   Bun 1.4.1/1.4.2, running from source (no compile)	PASS on both

   Crash (with --sourcemaps linked, hence real file names):

   TypeError: undefined is not an object (evaluating 'node.name')
       at resolve (packages/core/src/effect/layer-node.ts:241:45)   // replacementMap.get(node.name) ?? node
       at recur (layer-node.ts:185:28)                              // options.resolve?.(node) ?? node
       at map (native)
       at <anonymous> (layer-node.ts:239:57)                        // node.dependencies.map(context.visit)
       ...
       at SystemPrompt.environment (src/session/prompt.ts:1259)
   

   A node in the Effect layer graph is undefined — consistent with cross-chunk
   module-init ordering under ESM splitting in the compiled bundle. Not reproducible from
   source on the same Bun versions.

   One important note on reproduction: the crash only fires on an actual agent turn
   (prompt → system-prompt build → layer resolution). Route-level smoke tests
   (/health, /config, /agent) all return 200 on a broken binary — that may explain why
   the stock-source repro attempt above came back clean.

   Happy to help narrow further — the hoist/walk code in layer-node.ts around those
   lines is the failing site, and I can test candidate fixes or a minimized repro on darwin-arm64.
4. robobun

   added

   bugSomething isn't workingSomething isn't working

   bundlerSomething to do with the bundlerSomething to do with the bundler

   regression

   single-file-executablebun build --compilebun build --compile

   on Sep 20, 2026
5. johnnymo87

   added 3 commits that reference this issue on Sep 21, 2026

   fix: pin bun 1.4.0, not 1.4.2, and carry the SSE cancel-rejection bac…

   ...

   1235012

   docs: sharpen the bun-pin and tripwire comments after review

   ...

   7ee40b6

   [NO-JIRA] Build releases with bun 1.4.0 to stop the 1.5 GB/day /tmp l…

   ...

   32b64e5
6. Jarred-Sumner commented on Sep 26, 2026

   

   Jarred-Sumner

   on Sep 26, 2026

   Collaborator

   More actions

   Fixed in #42695

   👀React with 👀1Reacted by robobun
7. Jarred-Sumner

   closed this as completedon Sep 26, 2026
8. robobun commented on Sep 26, 2026

   

   robobun

   on Sep 26, 2026

   Collaborator

   More actions

   This is the same bug as #42632: with splitting: true, a chunk shared by several entry points could print an import cycle in the wrong order, so a hoisted var was read as undefined (node.name in layer-node.ts).

   #42695 fixes it and is merged into main (97246d0). I verified on main: test/bundler/bundler_splitting.test.ts passes, including the tests for this cycle. The fix is not in a tagged release yet (latest tag is 1.4.2). It is in canary (bun upgrade --canary) and ships in the next release.