In bun 1.3.4, sharp paackage is failing at build

[iajaysharma]

What version of Bun is running?

1.3.4

What platform is your computer?

No response

What steps can reproduce the bug?

115 | } 116 | help.push( 117 | '- Consult the installation documentation:', 118 | ' See https://sharp.pixelplumbing.com/install' 119 | ); 120 | throw new Error(help.join('\n')); ^ error: Could not load the "sharp" module using the linux-arm64 runtime Possible solutions: - Ensure optional dependencies can be installed: npm install --include=optional sharp - Ensure your package manager supports multi-platform installation: See https://sharp.pixelplumbing.com/install#cross-platform - Add platform-specific dependencies: npm install --os=linux --cpu=arm64 sharp - Consult the installation documentation: See https://sharp.pixelplumbing.com/install at (node_modules/sharp/lib/sharp.js:120:13) at (/$bunfs/root/myapp:2:353) at (node_modules/sharp/lib/constructor.js:8:7) at (/$bunfs/root/myapp:2:353) at (node_modules/sharp/lib/index.js:6:7) at (/$bunfs/root/myapp:2:353) at api/src/routes/admin/category.route.ts:5:1 at loadAndEvaluateModule (2:1) Bun v1.3.4 (Linux arm64) 115 | } 116 | help.push( 117 | '- Consult the installation documentation:', 118 | ' See https://sharp.pixelplumbing.com/install' 119 | ); 120 | throw new Error(help.join('\n')); ^ error: Could not load the "sharp" module using the linux-arm64 runtime Possible solutions: - Ensure optional dependencies can be installed: npm install --include=optional sharp - Ensure your package manager supports multi-platform installation: See https://sharp.pixelplumbing.com/install#cross-platform - Add platform-specific dependencies: npm install --os=linux --cpu=arm64 sharp - Consult the installation documentation: See https://sharp.pixelplumbing.com/install at (node_modules/sharp/lib/sharp.js:120:13) at (/$bunfs/root/myapp:2:353) at (node_modules/sharp/lib/constructor.js:8:7) at (/$bunfs/root/myapp:2:353) at (node_modules/sharp/lib/index.js:6:7) at (/$bunfs/root/myapp:2:353) at api/src/routes/admin/category.route.ts:5:1 at loadAndEvaluateModule (2:1) Bun v1.3.4 (Linux arm64) 115 | } 116 | help.push( 117 | '- Consult the installation documentation:', 118 | ' See https://sharp.pixelplumbing.com/install' 119 | ); 120 | throw new Error(help.join('\n')); ^ error: Could not load the "sharp" module using the linux-arm64 runtime Possible solutions: - Ensure optional dependencies can be installed: npm install --include=optional sharp - Ensure your package manager supports multi-platform installation: See https://sharp.pixelplumbing.com/install#cross-platform - Add platform-specific dependencies: npm install --os=linux --cpu=arm64 sharp - Consult the installation documentation: See https://sharp.pixelplumbing.com/install at (node_modules/sharp/lib/sharp.js:120:13) at (/$bunfs/root/myapp:2:353) at (node_modules/sharp/lib/constructor.js:8:7) at (/$bunfs/root/myapp:2:353) at (node_modules/sharp/lib/index.js:6:7) at (/$bunfs/root/myapp:2:353) at api/src/routes/admin/category.route.ts:5:1 at loadAndEvaluateModule (2:1) Bun v1.3.4 (Linux arm64) 115 | } 116 | help.push( 117 | '- Consult the installation documentation:', 118 | ' See https://sharp.pixelplumbing.com/install' 119 | ); 120 | throw new Error(help.join('\n')); ^ error: Could not load the "sharp" module using the linux-arm64 runtime Possible solutions: - Ensure optional dependencies can be installed: npm install --include=optional sharp - Ensure your package manager supports multi-platform installation: See https://sharp.pixelplumbing.com/install#cross-platform - Add platform-specific dependencies: npm install --os=linux --cpu=arm64 sharp - Consult the installation documentation: See https://sharp.pixelplumbing.com/install at (node_modules/sharp/lib/sharp.js:120:13) at (/$bunfs/root/myapp:2:353) at (node_modules/sharp/lib/constructor.js:8:7) at (/$bunfs/root/myapp:2:353) at (node_modules/sharp/lib/index.js:6:7) at (/$bunfs/root/myapp:2:353) at api/src/routes/admin/category.route.ts:5:1 at loadAndEvaluateModule (2:1) Bun v1.3.4 (Linux arm64) 115 | } 116 | help.push( 117 | '- Consult the installation documentation:', 118 | ' See https://sharp.pixelplumbing.com/install' 119 | ); 120 | throw new Error(help.join('\n')); ^ error: Could not load the "sharp" module using the linux-arm64 runtime Possible solutions: - Ensure optional dependencies can be installed: npm install --include=optional sharp - Ensure your package manager supports multi-platform installation: See https://sharp.pixelplumbing.com/install#cross-platform - Add platform-specific dependencies: npm install --os=linux --cpu=arm64 sharp - Consult the installation documentation: See https://sharp.pixelplumbing.com/install at (node_modules/sharp/lib/sharp.js:120:13) at (/$bunfs/root/myapp:2:353) at (node_modules/sharp/lib/constructor.js:8:7) at (/$bunfs/root/myapp:2:353) at (node_modules/sharp/lib/index.js:6:7) at (/$bunfs/root/myapp:2:353) at api/src/routes/admin/category.route.ts:5:1 at loadAndEvaluateModule (2:1) Bun v1.3.4 (Linux arm64) 115 | } 116 | help.push( 117 | '- Consult the installation documentation:', 118 | ' See https://sharp.pixelplumbing.com/install' 119 | ); 120 | throw new Error(help.join('\n')); ^ error: Could not load the "sharp" module using the linux-arm64 runtime Possible solutions: - Ensure optional dependencies can be installed: npm install --include=optional sharp - Ensure your package manager supports multi-platform installation: See https://sharp.pixelplumbing.com/install#cross-platform - Add platform-specific dependencies: npm install --os=linux --cpu=arm64 sharp - Consult the installation documentation: See https://sharp.pixelplumbing.com/install at (node_modules/sharp/lib/sharp.js:120:13) at (/$bunfs/root/myapp:2:353) at (node_modules/sharp/lib/constructor.js:8:7) at (/$bunfs/root/myapp:2:353) at (node_modules/sharp/lib/index.js:6:7) at (/$bunfs/root/myapp:2:353) at api/src/routes/admin/category.route.ts:5:1 at loadAndEvaluateModule (2:1) Bun v1.3.4 (Linux arm64) 115 | } 116 | help.push( 117 | '- Consult the installation documentation:', 118 | ' See https://sharp.pixelplumbing.com/install' 119 | ); 120 | throw new Error(help.join('\n')); ^ error: Could not load the "sharp" module using the linux-arm64 runtime Possible solutions: - Ensure optional dependencies can be installed: npm install --include=optional sharp - Ensure your package manager supports multi-platform installation: See https://sharp.pixelplumbing.com/install#cross-platform - Add platform-specific dependencies: npm install --os=linux --cpu=arm64 sharp - Consult the installation documentation: See https://sharp.pixelplumbing.com/install at (node_modules/sharp/lib/sharp.js:120:13) at (/$bunfs/root/myapp:2:353) at (node_modules/sharp/lib/constructor.js:8:7) at (/$bunfs/root/myapp:2:353) at (node_modules/sharp/lib/index.js:6:7) at (/$bunfs/root/myapp:2:353) at api/src/routes/admin/category.route.ts:5:1 at loadAndEvaluateModule (2:1) Bun v1.3.4 (Linux arm64) 115 | } 116 | help.push( 117 | '- Consult the installation documentation:', 118 | ' See https://sharp.pixelplumbing.com/install' 119 | ); 120 | throw new Error(help.join('\n')); ^ error: Could not load the "sharp" module using the linux-arm64 runtime Possible solutions: - Ensure optional dependencies can be installed: npm install --include=optional sharp - Ensure your package manager supports multi-platform installation: See https://sharp.pixelplumbing.com/install#cross-platform - Add platform-specific dependencies: npm install --os=linux --cpu=arm64 sharp - Consult the installation documentation: See https://sharp.pixelplumbing.com/install at (node_modules/sharp/lib/sharp.js:120:13) at (/$bunfs/root/myapp:2:353) at (node_modules/sharp/lib/constructor.js:8:7) at (/$bunfs/root/myapp:2:353) at (node_modules/sharp/lib/index.js:6:7) at (/$bunfs/root/myapp:2:353) at api/src/routes/admin/category.route.ts:5:1 at loadAndEvaluateModule (2:1) Bun v1.3.4 (Linux arm64) suddenly the bun build failing

In version 1.3.3 its working as expected.

What is the expected behavior?

Stage 1: Build

FROM oven/bun:1.3.3 AS build

WORKDIR /app

Copy only package files first for better caching

COPY ../package.json ./

Install dependencies

RUN bun install

Now copy the rest of the source files

COPY ../ .

ENV NODE_ENV=production

Compile the app

RUN bun build --compile --minify --sourcemap ./api/src/index.ts --outfile myapp --external cloudflare:workers

Set environment (optional)

EXPOSE 8080

CMD ["./myapp"]

above is the working Docckerfile but if we switch to 1.3.4, it will start failing due to sharp package

What do you see instead?

No response

Additional information

No response

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and agent prompts for this issue.

• Create Plan

Examples

• Example 1
• Example 2

🔗 Related PRs

#22365 - Fix Windows compilation issues with embedded resources and relative paths [merged] | src/StandaloneModuleGraph.zig:
"""

AI-generated summary of changes

• Public API: isBunStandaloneFilePath was renamed to isBunStandaloneFilePathCanonicalized, preserving the same prefix-based check against base_path and base_public_path logic.
• Public API: Added a new wrapper isBunStandaloneFilePath that, on Windows, canonicalizes input by removing NT path prefixes via strings.withoutNTPrefix before delegating to isBunStandaloneFilePathCanonicalized; on non-Windows, delegates directly to isBunStandaloneFilePathCanonicalized.
• Windows file move logic: Replaced the previous outfile handling path logic with a Windows-specific, absolute-destination approach. It now:
  • Determines the temp file path and current working directory.
  • Builds an absolute destination path (dest_path) from outfile and cwd if outfile is not absolute.
  • Converts both temp and dest paths to Windows UTF-16 and ensures null termination.
  • Closes the source fd before moving.
  • Moves the file using MoveFileExW with MOVEFILE_COPY_ALLOWED | MOVEFILE_REPLACE_EXISTING | MOVEFILE_WRITE_THROUGH.
  • Handles MoveFileExW failures by inspecting Win32 errors; maps EISDIR to a “is a directory” error, otherwise reports a move failure with the destination path.
• Windows metadata: After a successful move, Windows metadata is applied using the moved dest_path instead of a previously computed full path.
• General: Reworks toPath and related Windows-specific code paths to rely on absolute paths and explicit Windows APIs, replacing the prior approach that constructed an outfile_slice from basenameWindows and used a different move function.
• Small behavioral note: Windows NT-prefix handling for path checks is now centralized in the canonicalized function and the new wrapper handles Windows-specific canonicalization.

Alterations to the declarations of exported or public entities

• Method signature updated: pub fn isBunStandaloneFilePath(str: []const u8) bool in class StandaloneModuleGraph in src/StandaloneModuleGraph.zig → pub fn isBunStandaloneFilePathCanonicalized(str: []const u8) bool in class StandaloneModuleGraph in src/StandaloneModuleGraph.zig
• Method added: pub fn isBunStandaloneFilePath(str: []const u8) bool in class StandaloneModuleGraph in src/StandaloneModuleGraph.zig
  """

---

src/bundler/bundle_v2.zig:
"""

AI-generated summary of changes

• Public path handling adjusted for compile vs non-compile modes: in compile mode, transpiler.options.public_path is now derived from the target’s base public path (via StandaloneModuleGraph.targetBasePublicPath) instead of using the user config; in non-compile mode, the previous config.public_path is preserved.
• Output file path resolution hardened to always use absolute paths: full_outfile_path is now computed to always be absolute. If outdir is set, join as before; if outfile is already absolute, reuse it; otherwise, resolve relative to the current working directory (top_level_dir).
• Executable output path wiring updated: a new module_prefix is computed as StandaloneModuleGraph.targetBasePublicPath(compile_target.os, "root/") and passed as the 5th argument to toExecutable. The 6th argument is now outfile_for_executable, which is either the full_outfile_path on Windows or the basename on POSIX.
• OS-specific path handling for output directories refined: POSIX builds open/open-paths for root_dir when dirname is non-empty, using root_dir.makeOpenPath(dirname, …). Windows avoids changing root_dir when dirname is non-empty and ensures the directory exists via bun.makePath. This replaces the previous generic approach that altered root_dir for non-trivial dirname cases.
• Additional comments and guardrails added to clarify absolute path guarantees and Windows/POSIX divergences in path handling.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: High
"""

---

src/sys.zig:
"""

AI-generated summary of changes

• In moveFileZWithHandle, when renameat fails with XDEV, the code now performs a fallback copy (copyFileZSlowWithHandle) and unlink, then returns immediately with success instead of propagating the original error. This changes the control flow so a cross-device move that succeeds via the fallback path is treated as a successful operation.

• The added early return occurs only in the XDEV branch; the ISDIR and other error paths remain unchanged.

• The function signature and surrounding logic remain the same; only the post-fallback behavior in the XDEV path is modified.

Alterations to the declarations of exported or public entities

• No exported/public signatures were modified.

Estimated code review effort: Medium
"""

---

test/bundler/bun-build-compile-wasm.test.ts:
"""

AI-generated summary of changes

Introduces a new end-to-end test (test/bundler/bun-build-compile-wasm.test.ts) that verifies Bun.build can compile and execute a WebAssembly module embedded in a project. The test creates a temporary directory with two files: app.js (which imports and runs a WASM module) and test.wasm (a handcrafted minimal module exporting an add function). The app.js reads the wasm binary via Bun.file, Instantiates it with WebAssembly, calls the exported add(2,3) to obtain 5, logs the result, and exits with code 0 when the result is 5; otherwise it exits with 1 and logs errors. The test-wasm binary is provided as a Buffer.from of a minimal WASM module (type, function, export, code sections). The test then builds the project with Bun.build using entrypoint app.js and outfile app-wasm, asserts a single output and success, and runs the compiled binary with Bun.spawn. It captures stdout and stderr, waits for completion, and asserts exit code 0, stdout contains "WASM result: 5" and "WASM module loaded successfully", and stderr is empty. This validates the bundler’s ability to embed and execute a wasm module and ensures the module import path and runtime integration behave as expected. It also references a regression note in the test about module prefix handling.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Medium

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Medium
"""

---

test/bundler/bun-build-compile.test.ts:
"""

AI-generated summary of changes

Two new tests were added to test/bundler/bun-build-compile.test.ts under the Bun.build compile suite.

• compile with relative outfile paths:

  • Adds three sub-tests that build with relative outfile paths:
    • outfile: "output/nested/app1" and verifies the output path contains "output/nested/" depending on platform.
    • outfile: "./app2" and verifies the output path ends with "app2" or "app2.exe" on Windows.
    • outfile: "./a/b/c/d/app3" and verifies the output path contains "a/b/c/d/" depending on platform.
  • Each test asserts success and uses platform-aware path checks.

• compile with embedded resources uses correct module prefix:

  • Creates a dir with app.js that attempts to read an embedded.txt resource to exercise module/resource embedding behavior, plus an embedded.txt resource.
  • Builds with outfile: "app-with-resources" using the default target.
  • Asserts success, a single output, and that the output path ends with the correct executable extension for the platform.
  • Notes that success of compilation verifies the embedding path handling.

No changes to exported/public declarations are made in this diff.

Alterations to the declarations of exported or public entities

• No alterations to exported/public declarations.

Estimated code review effort: Medium
"""

---

test/regression/issue/compile-outfile-subdirs.test.ts:
"""

AI-generated summary of changes

A new test file test/regression/issue/compile-outfile-subdirs.test.ts adds comprehensive regression tests around compiling with nested outfile paths and the Bun.build API. The tests cover:

• compile with outfile using forward slash and backslash to ensure nested directories are created and the executable is placed under subdir/nested/app.exe; the tests run the produced executable to validate runtime output.
• creation of parent directories that do not exist yet (deeply nested outfile like a/b/c/d/e/app.exe) and verification that the final executable exists at the expected location.
• Windows-specific metadata handling: when Windows metadata options are supplied, the produced executable (e.g., output/bin/app.exe or dist/bin/app.exe in API tests) exists and VersionInfo fields (ProductName, FileDescription, ProductVersion) reflect the provided metadata.
• graceful failure when the parent path of the outfile is a file, expecting a non-zero exit and an error mentioning the path issue.
• handling of relative path components (.” and “..”) within outfile paths; normalization yields an expected final path (output/app.exe) and the file is created there.
• Bun.build API usage: tests ensure that specifying outfile via the API results in an executable under subdirectories (e.g., dist/bin/app.exe) and, on Windows, that metadata is applied similarly, with verification of VersionInfo fields.

The tests utilize Bun.spawn to run compile commands, verify exit codes and stderr, check file existence, run produced executables to verify runtime behavior, and, on Windows, query VersionInfo via PowerShell. They also employ conditional test blocks (test.if(isWindows)) to guard Windows-specific metadata checks. Overall, the changes introduce end-to-end validation of subdirectory output paths across CLI and API usage, including error handling and Windows metadata support.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: High
"""
#22651 - Fix Windows shell crash with && operator and external commands [merged] | src/shell/IO.zig:
"""

AI-generated summary of changes

• Modifies OutKind.to_subproc_stdio switch handling for the .fd case. Introduces a guarded path: if val.writer.fd.get() yields a valid FD, it now assigns .fd = fd; otherwise it falls back to the inherit path by setting .inherit = {}. This replaces the previous approach which unconditionally used val.writer.fd.get().? and could propagate an error or ignore the moved-to-libuv scenario.
• Adds a specific branch to handle a valid, unmoved FD and updates the Windows-related comment to reflect that if the FD has been moved to libuv, the subprocess should inherit stdio instead of using the FD.
• Overall change alters control flow from unconditionally attempting to unwrap a movable FD to a conditional path that either passes through a real FD or uses inheritance for Windows/libuv-managed cases.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: High
"""

---

test/regression/issue/22650-shell-crash.test.ts:
"""

AI-generated summary of changes

Adds a new regression test file test/regression/issue/22650-shell-crash.test.ts. The test uses bun:test with harness-provided bunEnv and bunExe. It defines a test named "issue #22650 - shell crash with && operator followed by external command" that spawns a Bun process via Bun.spawn with cmd [bunExe(), "exec", "echo test && node --version"], pipes stdout and stderr, and captures stdout, stderr, and exit code concurrently. It asserts: (1) no output on stderr, (2) stdout contains "test", (3) stdout matches the Node version pattern /v\d+.\d+.\d+/, and (4) exit code equals 0. The test verifies that chaining commands with && and invoking an external command does not crash the shell.

Alterations to the declarations of exported or public entities

• None (no exported/public declarations modified).

Estimated code review effort: Medium
"""

---

src/bun.js/event_loop/MiniEventLoop.zig:
"""

AI-generated summary of changes

• Adds a public API change to MiniEventLoop.initGlobal by introducing an optional cwd parameter and using it to initialize top_level_dir during initialization. The function signature changes from pub fn initGlobal(env: ?*bun.DotEnv.Loader) *MiniEventLoop to pub fn initGlobal(env: ?*bun.DotEnv.Loader, cwd: ?[]const u8) *MiniEventLoop. If cwd is provided, top_level_dir is set from it. If not, and top_level_dir is still empty, it queries the current working directory via bun.sys.getcwd into a PathBuffer, duplicates the path into global.top_level_dir using the default allocator, and falls back to an empty string on failure. This initialization block runs before globalInitialized is set to true, ensuring top_level_dir has a deterministic value during startup. No other public API changes are introduced; only initialization logic and the API signature are modified.

Alterations to the declarations of exported or public entities

• Method signature updated: pub fn initGlobal(env: ?*bun.DotEnv.Loader) *MiniEventLoop in src/bun.js/event_loop/MiniEventLoop.zig → pub fn initGlobal(env: ?*bun.DotEnv.Loader, cwd: ?[]const u8) *MiniEventLoop
  """

---

src/bun.js.zig:
"""

AI-generated summary of changes

In bootBunShell, the call to MiniEventLoop.initGlobal now passes a second argument. Previously: initGlobal(bundle.env). Now: initGlobal(bundle.env, null). The rest of the initialization flow is unchanged (top_level_dir assignment and interpreter startup from the entry file). This indicates a public API change to MiniEventLoop.initGlobal to accept an additional parameter, with the patch providing null for that parameter.

Alterations to the declarations of exported or public entities

• Public API change: jsc.MiniEventLoop.initGlobal signature updated to accept an additional parameter; call-site updated to pass null as the second argument in src/bun.js.zig (from initGlobal(bundle.env) to initGlobal(bundle.env, null)).

Estimated code review effort: Medium
"""

---

src/cli/bunx_command.zig:
"""

AI-generated summary of changes

In the Windows path of BunxCommand, the EventLoopHandle initialization now calls MiniEventLoop.initGlobal with an extra argument (null). This changes the call site from initGlobal(this_transpiler.env) to initGlobal(this_transpiler.env, null) when constructing the event loop for bunx install. No other logic or error handling in the diff is affected.

Alterations to the declarations of exported or public entities

• Method signature updated: bun.jsc.MiniEventLoop.initGlobal now accepts an additional parameter (two-argument form) instead of the previous one-argument form; the code uses initGlobal(this_transpiler.env, null) in src/cli/bunx_command.zig.

Estimated code review effort: Medium
"""

---

src/cli/create_command.zig:
"""

AI-generated summary of changes

• Updated Windows-specific event loop initialization to call MiniEventLoop.initGlobal with an extra argument. Replaced initGlobal(null) with initGlobal(null, null) in two call sites within src/cli/create_command.zig, leaving all other logic intact.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Medium
"""

---

src/cli/exec_command.zig:
"""

AI-generated summary of changes

• Introduces retrieval of the current working directory (cwd) via bun.sys.getcwd and uses the resulting path in the script execution flow, including building script_path and the parts array.
• Updates the MiniEventLoop initialization to pass the cwd: from initGlobal(bundle.env) to initGlobal(bundle.env, cwd).
• Ensures the cwd value is computed before using it to initialize the MiniEventLoop and to construct script-related paths.
• Error handling for cwd retrieval remains: on failure, emit an error and exit.
• No changes to the public API of ExecCommand.exec; the change is internal to how the environment and cwd are handled.

Alterations to the declarations of exported or public entities

• Signature updated: bun.jsc.MiniEventLoop.initGlobal(bundle.env) → bun.jsc.MiniEventLoop.initGlobal(bundle.env, cwd)

Estimated code review effort: Medium
"""

---

src/cli/filter_run.zig:
"""

AI-generated summary of changes

• The event loop initialization call changed from bun.jsc.MiniEventLoop.initGlobal(this_transpiler.env) to bun.jsc.MiniEventLoop.initGlobal(this_transpiler.env, null). This adds a second argument (null) to the initialization call; no other logic or control-flow changes are evident.

Alterations to the declarations of exported or public entities

• No exported/public declarations modified.

Estimated code review effort: Medium
"""

---

src/cli/pm_version_command.zig:
"""

AI-generated summary of changes

• Windows-specific event loop initialization in PmVersionCommand was updated across five call sites to pass an additional null argument to MiniEventLoop.initGlobal. Previously initGlobal(null) is now initGlobal(null, null). The second argument is consistently null. All other logic and error handling remain unchanged, and non-Windows paths are unaffected.

Alterations to the declarations of exported or public entities

• None (no changes to signatures of exported/public entities).

Estimated code review effort: Medium
"""

---

src/cli/run_command.zig:
"""

AI-generated summary of changes

• Non-system-shell script execution now passes the current working directory to MiniEventLoop.initGlobal by switching from initGlobal(env) to initGlobal(env, cwd) in RunPackageScriptForeground.
• Windows spawn paths updated to use initGlobal(env, null) to accommodate the new signature when no cwd is available, affecting both the RunPackageScriptForeground spawn path and the runBinaryWithoutBunxPath path.
• Overall, three call-sites are updated to accommodate a second, optional parameter for the MiniEventLoop initialization; no other logic or error handling changes are introduced.

Alterations to the declarations of exported or public entities

• Method signature updated: pub fn initGlobal in module bun.jsc.MiniEventLoop now accepts an additional parameter cwd: ?[]const u8 (previously it was initGlobal(env)).
  • Old: initGlobal(env: *DotEnv.Loader) ...
  • New: initGlobal(env: *DotEnv.Loader, cwd: ?[]const u8) ...

Estimated code review effort: Medium
"""

---

src/cli/upgrade_command.zig:
"""

AI-generated summary of changes

On Windows, the upgrade command’s Expand-Archive path now initializes the event loop with MiniEventLoop.initGlobal(null, null) instead of MiniEventLoop.initGlobal(null). This changes the EventLoopHandle creation for the spawned process; all other logic, including error handling and the surrounding control flow, remains unchanged.

• No changes to signatures of exported or public entities.

Estimated code review effort: Medium
"""

---

src/create/SourceFileProjectGenerator.zig:
"""

AI-generated summary of changes

• Windows-specific Event Loop initialization now passes an extra argument to MiniEventLoop.initGlobal in two call sites, changing from initGlobal(null) to initGlobal(null, null). The surrounding logic and error handling remain unchanged; only the function call signature at these two places is updated to match a newer API.

Alterations to the declarations of exported or public entities

• Method signature updated: bun.jsc.MiniEventLoop.initGlobal now accepts two parameters (previously one). This change requires updated call sites to provide an additional argument.
  • Updated call-site: src/create/SourceFileProjectGenerator.zig (Windows path) in two locations:
    • .windows = if (Environment.isWindows) .{ .loop = bun.jsc.EventLoopHandle.init(bun.jsc.MiniEventLoop.initGlobal(null, null)), }
    • (Second occurrence mirrors the same signature change)

Estimated code review effort: Medium
"""

---

src/http/HTTPThread.zig:
"""

AI-generated summary of changes

The only observable change is in onStart: the call to bun.jsc.MiniEventLoop.initGlobal now passes two arguments (null, null) instead of a single argument (null). This implies a public API change to MiniEventLoop.initGlobal. All other startup logic and control flow remain unchanged.

Alterations to the declarations of exported or public entities

• Function signature updated: bun.jsc.MiniEventLoop.initGlobal now takes two arguments instead of one.

Estimated code review effort: Medium
"""

---

src/open.zig:
"""

AI-generated summary of changes

In the Windows path of openURL, the initialization of the event loop now calls MiniEventLoop.initGlobal with an extra null argument, changing from initGlobal(null) to initGlobal(null, null). All other logic and control flow around the spawnSync call remains unchanged.

• Method signature updated: bun.jsc.MiniEventLoop.initGlobal(null) in src/open.zig → bun.jsc.MiniEventLoop.initGlobal(null, null) in src/open.zig

• Method signature updated: bun.jsc.MiniEventLoop.initGlobal(null) in src/open.zig → bun.jsc.MiniEventLoop.initGlobal(null, null) in src/open.zig

Estimated code review effort: Medium
"""
#23344 - fix(windows): handle UV_ENOTCONN gracefully when spawning with long cwd [merged] | src/bun.js/api/bun/subprocess.zig:
"""

AI-generated summary of changes

• Replaced assert-based error handling for starting stdio streams with explicit asErr() checks. If start(subprocess, loop) or start(subprocess.killSignal) returns an error, the code now kills the subprocess, converts the error to a JS error, and returns JSError, instead of asserting. This affects stdin.buffer.start, stdout.pipe.start, and stderr.pipe.start paths.
• Maintains existing subsequent logic for reading from pipes (readAll) only when appropriate (unchanged conditional flow), but branches into explicit error handling rather than assertion failure.

Alterations to the declarations of exported or public entities

• No changes to signatures of exported/public entities detected.

Estimated code review effort: Medium
"""

---

test/regression/issue/23316-long-path-spawn.test.ts:
"""

AI-generated summary of changes

Adds a new Windows-focused regression test file test/regression/issue/23316-long-path-spawn.test.ts containing two tests that verify Bun spawn behavior with long or 8.3-disabled Windows paths. Both tests are guarded by a Windows check and construct deeply nested directories to exceed or approach MAX_PATH, then attempt to spawn or copy with a working directory set to the deep path. The tests assert that operations either succeed without panicking or fail with a non-panic, Error instance. The first test builds a path exceeding 260 characters, spawns a process with that cwd, and ensures the outcome is either a successful spawn or a non-panicking error path. The second test creates a deep path, writes a test.js file there, and spawns a process using that path, asserting that errors are non-panic and are Error instances as appropriate. Both tests use Bun.write to create auxiliary files and Bun.spawn to run commands, with stdout/stderr handling specified.

Alterations to the declarations of exported or public entities

• No exported/public declarations changed
  """

---

src/bun.js/webcore/Blob.zig:
"""

AI-generated summary of changes

• In writeFileWithSourceDestination Windows path, wrap the WriteFileWindows.create call with a catch block to swallow WriteFileWindowsDeinitialized error, preventing propagation.

Alterations to the declarations of exported or public entities

Estimated code review effort: Medium
"""

---

src/bun.js/webcore/blob/write_file.zig:
"""

AI-generated summary of changes

• Introduces a new public error type WriteFileWindowsError = error{WriteFileWindowsDeinitialized}.
• Change of public API surface: createWithCtx in WriteFileWindows now returns WriteFileWindowsError!*WriteFileWindows instead of *WriteFileWindows.
• Change of public API surface: open method on WriteFileWindows now returns WriteFileWindowsError!void instead of void.
• Change of public API surface: doWriteLoop now returns WriteFileWindowsError!void instead of void.
• Change of public API surface: onFinish now returns WriteFileWindowsError instead of void.
• Change of public API surface: runFromJSThread now returns WriteFileWindowsError instead of void.
• Change of public API surface: throw now returns WriteFileWindowsError instead of void.
• Several call sites updated to propagate the new error type (e.g., using try, return this.throw(...), and catch blocks for error.WriteFileWindowsDeinitialized).
• Control flow updated to swallow error.WriteFileWindowsDeinitialized in multiple branches via catch blocks, and to return the new error type from several functions.
• Initialization path adjusted in createWithCtx/open/loop flows to use try/catch with the new WriteFileWindowsError handling, including in mkdirp and open-related paths.
• toSystemError and other utility logic updated to align with the new error propagation, including path/fd handling via a switch over pathlike.
• Minor adjustments to ensure deinitialization paths are guarded by the new error type and that finishing paths return the appropriate error-aware results.

Alterations to the declarations of exported or public entities

• Added public error set: WriteFileWindowsError = error{WriteFileWindowsDeinitialized} inside the WriteFileWindows scope.
• Signature changed: pub fn createWithCtx(...) !*WriteFileWindows in the WriteFileWindows struct (formerly *WriteFileWindows).
• Signature changed: pub fn open(this: *WriteFileWindows) WriteFileWindowsError!void (formerly void).
• Signature changed: pub fn doWriteLoop(this: *WriteFileWindows, uv_loop: *uv.Loop) WriteFileWindowsError!void (formerly void).
• Signature changed: pub fn onFinish(container: *WriteFileWindows) WriteFileWindowsError (formerly void).
• Signature changed: pub fn runFromJSThread(this: *WriteFileWindows) WriteFileWindowsError (formerly void).
• Signature changed: pub fn throw(this: *WriteFileWindows, err: bun.sys.Error) WriteFileWindowsError (formerly void).
• Signature changed: pub fn create(...) WriteFileWindowsError!*WriteFileWindows (previously )!*WriteFileWindows).
• Signature changed: pub fn createWithCtx(...) in the top of WriteFileWindows now returns WriteFileWindowsError!*WriteFileWindows (as above).
• Signature changes propagate: various internal calls now return or throw WriteFileWindowsError and callers handle with try/catch blocks.
• Added error-handling propagation in multiple internal helpers (e.g., onOpen, onWriteComplete) to convert and propagate errors using the new WriteFileWindowsError.

Estimated code review effort: High
"""
#24236 - add "configVersion" to bun.lock(b) [merged] | src/install/PackageManager/PackageManagerOptions.zig:
"""

AI-generated summary of changes

• Adds a new field config_version of type ?bun.ConfigVersion with default null to the Options struct in src/install/PackageManager/PackageManagerOptions.zig, positioned before PublishConfig. This is a semantic extension to hold a configuration version; no other behavioral changes are introduced.

Alterations to the declarations of exported or public entities

• Field added: config_version: ?bun.ConfigVersion = null in struct Options in file src/install/PackageManager/PackageManagerOptions.zig

Estimated code review effort: Medium

Estimated code review effort: Medium
"""

---

src/install/PackageManager/install_with_manager.zig:
"""

AI-generated summary of changes

• Added: determine and apply a configuration version by calling load_result.chooseConfigVersion() and assigning it to manager.options.config_version.
• Control flow change: in the node_linker auto branch, replace inline branching with a config_version-driven decision path:
  • For .v0: continue as hoisted.
  • For .v1: if not migratedFromNpm() and there are workspace paths, go isolated; otherwise hoisted.
• Side effect: propagate the changed_config_version flag to force saving the lockfile when the configuration version changes.
• Public API surface changes: introduce a public method chooseConfigVersion() on the LoadResult type that returns a ConfigVersion (.v0 or .v1).

Alterations to the declarations of exported or public entities

• Added: field config_version to PackageManager.Options (in file src/install/PackageManager/install_with_manager.zig), type ConfigVersion.
• Added: method chooseConfigVersion() to type Lockfile.LoadResult (or equivalent load result type used here), returning a ConfigVersion with possible values .v0 and .v1.
  """

---

src/install/lockfile.zig:
"""

AI-generated summary of changes

• Added a new public field saved_config_version: ?bun.ConfigVersion to Lockfile.
• Added a new public method chooseConfigVersion(this: *const LoadResult) struct { bun.ConfigVersion, bool } on LoadResult union to derive the effective config version from migration state and saved_config_version.
• Updated loadFromDir to pass &manager.?.options to TextLockfile.Stringifier.saveFromBinary, adding an options parameter to the binary-to-text conversion path.
• Updated saveToDisk to pass options to TextLockfile.Stringifier.saveFromBinary and to Lockfile.Serializer.save, changing parameter sets from a verbose flag to an options struct.
• Updated initEmpty to initialize saved_config_version to null, providing a defined default.

Alterations to the declarations of exported or public entities

• Added public field: saved_config_version: ?bun.ConfigVersion in struct Lockfile (src/install/lockfile.zig)
• Added public method: pub fn chooseConfigVersion(this: *const LoadResult) struct { bun.ConfigVersion, bool } in union LoadResult (src/install/lockfile.zig)

Manifest File Analyzer

NONE
"""

---

src/install/lockfile/Buffers.zig:
"""

AI-generated summary of changes

• Replaced the verbose_log boolean parameter in Buffers.zig's save function with a new options pointer (options: *const PackageManager.Options).

• Updated the logging condition inside save from if (verbose_log) to if (options.log_level.isVerbose()) to control verbose output via the new options parameter.

• Method signature updated: def coderabbit_formula(x, y) in class Calculator in src/calculator.py → def coderabbit_formula(x, y, z) in class Calculator in src/calculator.py

Estimated code review effort: Medium
"""

---

src/install/lockfile/bun.lock.zig:
"""

AI-generated summary of changes

• Public API change: Stringifier.saveFromBinary now accepts an additional parameter options: *const PackageManager.Options, in addition to the existing allocator, lockfile, and load_result.
• Output augmentation: In saveFromBinary, writes a new configVersion field derived from options.config_version (or current if absent) alongside existing fields.
• ConfigVersion error signaling added: ParseError gains a new variant InvalidConfigVersion.
• ConfigVersion parsing support added: In parseIntoBinaryLockfile, the parser now optionally reads a top-level "configVersion" from the root and assigns it to lockfile.saved_config_version using bun.ConfigVersion.fromExpr, producing InvalidConfigVersion on failure.

Alterations to the declarations of exported or public entities

• Method signature updated: pub fn saveFromBinary(allocator: std.mem.Allocator, lockfile: *BinaryLockfile, load_result: *const LoadResult, writer: anytype) @TypeOf(writer).Error!void in src/install/lockfile/bun.lock.zig → pub fn saveFromBinary(allocator: std.mem.Allocator, lockfile: *BinaryLockfile, load_result: *const LoadResult, options: *const PackageManager.Options, writer: anytype) @TypeOf(writer).Error!void
• Enum variant added: InvalidConfigVersion to ParseError in src/install/lockfile/bun.lock.zig

Manifest File Analyzer

"""

---

src/install/lockfile/bun.lockb.zig:
"""

AI-generated summary of changes

• Introduces a new config version tag and writes/reads a config_version field in the bun lockfile format.
• Updates public save function signature from (this, verbose_log, ...) to (this, options, ...), and updates internal calls to pass options where verbose_log was used.
• Writes a config version section during save using options.config_version (or current if absent).
• During load, adds logic to detect and read the has_config_version_tag, parsing the config version and storing it in lockfile.saved_config_version.
• Retains existing data sections and adds preliminary handling for the config version in the read path, ensuring compatibility with the new tag.
• Minor control-flow adjustments to accommodate the optional config version data during both save and load paths.

Alterations to the declarations of exported or public entities

• Method signature updated:
  • from: pub fn save(this: *Lockfile, verbose_log: bool, bytes: *std.ArrayList(u8), total_size: *usize, end_pos: *usize) !void
  • to: pub fn save(this: *Lockfile, options: *const PackageManager.Options, bytes: *std.ArrayList(u8), total_size: *usize, end_pos: *usize) !void

Estimated code review effort: Medium
"""

---

src/ConfigVersion.zig:
"""

AI-generated summary of changes

Introduces a new Zig file defining an exported enum ConfigVersion with variants v0 and v1 and a current alias set to v1. Adds two public constructors:

• fromExpr(expr: bun.ast.Expr) ?ConfigVersion: accepts an AST expression; returns a ConfigVersion for numeric literals 0 or 1, returns null for non-number expressions, out-of-range values, or non-integer representations; clamps values greater than current to current.
• fromInt(int: u64) ?ConfigVersion: returns v0 for 0, v1 for 1, returns current for values greater than current, otherwise null for invalid values.

Includes a guard against non-integer expressions, and handles edge cases by returning null or current as appropriate. Exposes a constant current as .v1. Imports bun via bun = @import("bun").

Alterations to the declarations of exported or public entities

• Public enum added: ConfigVersion in src/ConfigVersion.zig
• Public constant added: current with value .v1 inside ConfigVersion
• Public function added: pub fn fromExpr(expr: bun.ast.Expr) ?ConfigVersion in ConfigVersion
• Public function added: pub fn fromInt(int: u64) ?ConfigVersion in ConfigVersion

Note: All changes pertain to the newly declared/public entity ConfigVersion and its associated public methods and constant.

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

src/bun.zig:
"""

AI-generated summary of changes

• Added a new public constant ConfigVersion in src/bun.zig, exposing ConfigVersion by importing from ./ConfigVersion.zig.ConfigVersion. This addition appears twice in the file (two separate declarations), introducing publicly accessible symbols without altering existing logic or control flow.

• Alterations to the declarations of exported or public entities
  • Added: pub const ConfigVersion = @import("./ConfigVersion.zig").ConfigVersion; in src/bun.zig
  • Added: pub const ConfigVersion = @import("./ConfigVersion.zig").ConfigVersion; in src/bun.zig (second occurrence, at the end of the file)

Estimated code review effort: Medium
"""

---

test/cli/install/config-version.test.ts:
"""

AI-generated summary of changes

Adds a new test file test/cli/install/config-version.test.ts that spins up a Verdaccio registry and validates Bun install behavior around configVersion in various scenarios:

• A simple project with a direct dependency, asserting absence/presence of node_modules/.bun and the installed package.json, and verifying bun.lock contents and inline snapshot structure.
• A monorepo setup using workspaces with isolated linking, validating workspace resolution and corresponding lockfile entries.
• Updating an existing lockfile to include configVersion, ensuring hoisted installs where applicable and corresponding lockfile adjustments, including an updated lockfile inline snapshot with configVersion changes.
  Uses beforeAll/afterAll lifecycle hooks to manage the registry and Bun install invocations, and employs file existence checks, JSON reads, and inline snapshots for bun.lock structure.

Alterations to the declarations of exported or public entities

• None (no exported/public declarations modified)

Manifest File Analyzer

Estimated code review effort: High
"""

---

test/cli/install/migration/pnpm-migration.test.ts:
"""

AI-generated summary of changes

• In test/cli/install/migration/pnpm-migration.test.ts, multiple test cases now pass bunfigOpts: { linker: "hoisted" } to Verdaccio's createTestDir, replacing previous calls that did not supply bunfigOpts. This changes the test setup configuration without altering test logic or assertions. The observable effect is that the test environments are created with a hoisted Bun linker, affecting how dependencies are installed within those tests. No changes to runtime behavior outside test setup.

Alterations to the declarations of exported or public entities

• No changes to exported or public declarations detected.

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

test/harness.ts:
"""

AI-generated summary of changes

• Public BunfigOpts type signature updated: isolated?: boolean → linker?: "isolated" | "hoisted". This changes the exposed configuration for bunfig options from a boolean flag to an explicit linker mode.
• createTestDir default options updated to include a default bunfigOpts with linker: "hoisted", and to initialize files to an empty object when not provided.
• bunfig generation logic adjusted to emit linker setting only when opts.linker is provided (instead of always emitting a potentially derived value from isolated/hoisted).
• writeBunfig logic updated to conditionally include linker configuration based on the new opts.linker field.
• No other public signatures changed beyond BunfigOpts.

Alterations to the declarations of exported or public entities

• Type updated: BunfigOpts in Verdaccio-related test utilities
  • Before: isolated?: boolean
  • After: linker?: "isolated" | "hoisted"

Estimated code review effort: Junior
"""

---

test/cli/install/minimum-release-age.test.ts:
"""

AI-generated summary of changes

• In the monorepo minimum-release-age test snapshot, the emitted lockfile snapshot now includes a new top-level field configVersion: 1. This is an addition to the existing JSON snapshot; no behavioral changes to code paths, only the expected snapshot output.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Low
"""

---

test/cli/install/bun-patch.test.ts:
"""

AI-generated summary of changes

• Introduced the --linker hoisted flag to several Bun CLI invocations within tests. Specifically:
  • bun i commands now run with i --linker hoisted.
  • bun patch commands now run with patch --linker hoisted.
  • bun i commands inside scenarios with --backend hardlink now use i --backend hardlink --linker hoisted.
  • bun patch invocations that overwrite or commit changes now include --linker hoisted where patches are applied, including nested and multi-path scenarios.
• Updated test expectations and interactions to align with the added --linker hoisted flag (e.g., propagation of patch paths and the handling of patch commits remains validated, now under the augmented command line).
• Some occurrences also add the flag in conjunction with existing --backend hardlink to ensure lockfile handling remains correct when using the hoisted linker strategy.

Alterations to the declarations of exported or public entities

• None

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

test/cli/install/bun-workspaces.test.ts:
"""

AI-generated summary of changes

• Updated test snapshots to expect a new root-level field in the lockfile JSON: configVersion: 1. The added field is present in the edited inline snapshot blocks, increasing the observed lockfile structure. No behavioral changes to code paths; only test expectations are adjusted to reflect the additional configVersion property.

Alterations to the declarations of exported or public entities

• None

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

test/cli/install/catalogs.test.ts:
"""

AI-generated summary of changes

• In test/cli/install/catalogs.test.ts, when creating the test directory via registry.createTestDir, the bunfigOpts now include linker: "hoisted" in addition to saveTextLockfile (which remains toggled as before). This changes the configuration passed to the test environment setup.

Estimated code review effort: Medium
"""

---

test/bake/bake-harness.ts:
"""

AI-generated summary of changes

• Adds the --linker=hoisted option to Bun install invocations when installing React-related packages, in three places: (1) the in-temp-install path during cache population, (2) the ensureReactCache path during a fresh install to populate the cache, and (3) the Bun spawn used for bun install in test harness when dependencies are linked from the project root. The changes modify the installation commands only, preserving all subsequent copy/cache logic and error handling.

Alterations to the declarations of exported or public entities

• None

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

test/bundler/expectBundled.ts:
"""

AI-generated summary of changes

• Adds the --linker=hoisted flag to the Bun install command when preparing the test root, affecting dependency installation behavior without modifying other logic or error handling paths.

Alterations to the declarations of exported or public entities

• No public/exported entity signatures modified.

Estimated code review effort: Medium
"""

---

test/cli/install/bun-add.test.ts:
"""

AI-generated summary of changes

• In beforeEach, dummyBeforeEach now called with { linker: "hoisted" } instead of no arguments.
• bun add invocations updated to include explicit linker flags:
  • bun add ... baz now uses --linker=isolated in tests for workspaces scenario.
  • bun add ... dep updated to include --linker=isolated.
  • bun add ... ${server_url}/parent.tgz updated to include --linker=hoisted.
  • bun add ... dep in workspace-direct install test updated to include --linker=isolated.
  • bun add ... parent.tgz in tarball test updated to include --linker=hoisted.
• Overall, the changes switch several dependency installation commands to use explicit linker strategies (isolated or hoisted), affecting the observed install output and filesystem layout in tests, without altering test logic otherwise.

Alterations to the declarations of exported or public entities

• No changes to signatures of exported/public entities

Estimated code review effort: Medium

Estimated code review effort: Medium
"""

---

test/cli/install/bun-install-cpu-os.test.ts:
"""

AI-generated summary of changes

• Changed pre-test setup to call dummyBeforeEach({ linker: "hoisted" }) instead of dummyBeforeEach(), introducing a linker configuration in the test bootstrap.

Alterations to the declarations of exported or public entities

• Method signature updated: dummyBeforeEach in module ./dummy.registry.js now accepts an options object with a linker property (e.g., { linker: "hoisted" }). Previously it accepted no arguments.

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

test/cli/install/bun-install-lifecycle-scripts.test.ts:
"""

AI-generated summary of changes

• Extends test setup to pass bunfigOpts with linker set to hoisted when creating a test directory, affecting the environment used for package installation.
• Adds linker: "hoisted" to Bunfig configuration when writing Bunfig via Verdaccio writeBunfig in multiple install lifecycle scenarios, ensuring hoisted linker is used during those runs.

Alterations to the declarations of exported or public entities

• Method signature updated: VerdaccioRegistry.createTestDir(...) → now accepts an options object (e.g., { bunfigOpts: { linker: "hoisted" } }).
• Method signature updated: VerdaccioRegistry.writeBunfig(...) → now accepts an options object that can include saveTextLockfile and linker (e.g., { saveTextLockfile: false, linker: "hoisted" }).

Estimated code review effort: Medium
"""

---

test/cli/install/bun-install-patch.test.ts:
"""

AI-generated summary of changes

• Minor test adjustment: the bun install command in bun-install-patch.test.ts now runs with an additional flag --linker=hoisted. No other logic, error handling, or control flow changes; the modification only affects the installer invocation within the negative patch-injection scenario.

Alterations to the declarations of exported or public entities

• (none)

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

test/cli/install/bun-install-registry.test.ts:
"""

AI-generated summary of changes

• Test setup changes:
  • beforeEach now creates test directory with bunfigOpts including linker: "hoisted" in addition to saveTextLockfile: false.
• Test commands updated to use hoisted linker:
  • bun install invocations updated to include --linker=hoisted (e.g., bun install, bun i) in multiple tests.
  • bunfig.toml related invocations updated to pass linker flag where appropriate.
  • bun spawn/test bin invocations updated to append --linker=hoisted in various places (e.g., both global and local install paths).
• Execution/verification adjustments:
  • Several test expectations updated to reflect hoisted linker usage (e.g., test output lines now show dependencies installed with hoisted linker considerations).
• Manifest/lockfile data changes:
  • In one test, an added configVersion field (configVersion: 1) appears in an existing lockfile snippet to reflect versioned config compatibility.
• Public API surface:
  • No public API declarations changed; changes are confined to test behavior and test data.

Alterations to the declarations of exported or public entities

• Public API signatures changed: none

Manifest File Analyzer

"""

---

test/cli/install/bun-install-retry.test.ts:
"""

AI-generated summary of changes

• Test change: In bun-install-retry.test.ts, the command to install BaR now includes the flag --linker=hoisted, altering how the package is linked during the test run.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Medium
"""

---

test/cli/install/bun-install.test.ts:
"""

AI-generated summary of changes

• Added the CLI option "--linker=hoisted" to bun install invocations in multiple test cases, changing the linker mode used during installation.
• Updated expectations to reflect an added "configVersion": 1 in bun.lock and bun.lockb snapshots, indicating an extra configuration version entry in lockfiles.

Alterations to the declarations of exported or public entities

• None

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

test/cli/install/bun-update.test.ts:
"""

AI-generated summary of changes

• Added the CLI flag --linker=hoisted to multiple bun install and bun update invocations in the tests, replacing prior invocations without the flag.
• Removed a stray console.log({ package_dir }) from the test setup.

These changes alter the command-line arguments used during test executions (control flow remains the same, but the dependency installation/update paths may differ due to the hoisted linker behavior). No changes to public APIs or exported declarations.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Medium
"""

---

test/cli/install/overrides.test.ts:
"""

AI-generated summary of changes

• install() now invokes bun with an additional argument --linker=hoisted, altering the linker mode used during install. installExpectFail() remains unchanged. No other logic, error handling, or control flow modifications.

Alterations to the declarations of exported or public entities

• No exported/public declarations were changed.

Estimated code review effort: Medium
"""

---

test/integration/esbuild/esbuild.test.ts:
"""

AI-generated summary of changes

Changed the working directory for the esbuild version check from a nested node_modules path using multiple segments to a single joined path string. Functionally equivalent on POSIX, with no other logic or error-handling changes.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Medium
"""

---

test/regression/issue/08093.test.ts:
"""

AI-generated summary of changes

• In the test, the bun install command gains an additional flag --linker=hoisted, changing invocation behavior from "bun install --backend hardlink" to "bun install --backend hardlink --linker=hoisted". This affects how links are created during installation, without altering other test logic or expectations.

Alterations to the declarations of exported or public entities

• (no exported/public entity declarations changed)

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

test/cli/install/bun-link.test.ts:
"""

AI-generated summary of changes

• Sets the test environment to use the hoisted linker by default by passing { linker: "hoisted" } to dummyBeforeEach in setup.
• Updates two test cases to explicitly use the hoisted linker when linking workspace packages by adding the flag --linker=hoisted to bun link invocations (for moo and for foo).
• The net effect is consistent adoption of the hoisted linker in both setup and relevant link operations, ensuring the same linker mode across tests.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Medium
"""

---

test/regression/issue/patch-bounds-check.test.ts:
"""

AI-generated summary of changes

• Replaced three occurrences of the Bun install command with an augmented form that adds the --linker=hoisted flag: from [bunExe(), "install"] to [bunExe(), "install", "--linker=hoisted"]. This affects setup/installation behavior during tests but not the test structure or assertions.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Medium
"""

---

test/js/bun/shell/commands/rm.test.ts:
"""

AI-generated summary of changes

The bun install command in the rm test is updated to use --linker hoisted; the rest of the command sequence remains the same, preserving temporary directory setup, node_modules check, and test execution. This changes the control flow of the install step and error output redirection remains. No other behavior changes.

• No public/exported-entity signature changes.

Estimated code review effort: Medium
"""

---

test/cli/install/isolated-install.test.ts:
"""

AI-generated summary of changes

• Replaced all occurrences of bunfigOpts: { isolated: true } with bunfigOpts: { linker: "isolated" } across test cases, effectively switching the isolation mechanism invoked by the test harness from a boolean flag to a linker-based option.

• All functional behavior remains the same from the tests’ perspective, but the configuration pathway for enabling isolated linking changes (control flow relies on the linker option rather than an isolated flag).

• Method signature updated: VerdaccioRegistry.createTestDir (in test harness) now accepts bunfigOpts with { linker: "isolated" } in place of the previous { isolated: true }. This changes the public/options surface of the test helper without altering the method name or core usage pattern.

Estimated code review effort: Medium
"""

---

test/cli/install/public-hoist-pattern.test.ts:
"""

AI-generated summary of changes

• Replaced bunfigOpts: { isolated: true, ... } with bunfigOpts: { linker: "isolated", ... } across multiple test cases. The observable change is substituting a boolean flag for a named linker field while preserving the rest of the configuration (e.g., publicHoistPattern). This affects how the test harness reads the configuration but not the surrounding test logic or assertions. Several tests that previously relied on isolated mode now explicitly set linker: "isolated". Error-case tests updated accordingly to reflect the new structure (e.g., bunfig.toml containing linker = "isolated" and publicHoistPattern values). Overall control flow and expectations remain the same; only the configuration shape changes.

Alterations to the declarations of exported or public entities

• None

Manifest File Analyzer

Estimated code review effort: Medium
"""
#24719 - docs: re-apply many recent changes that somehow aren't present [merged] | docs/bundler/executables.mdx:
"""

AI-generated summary of changes

• Added a Code splitting documentation block describing how to use bun build --compile with --splitting, including example commands, code samples, and expected output.
• Duplicated the Code splitting documentation block, appearing in two locations.
• Updated the Unsupported CLI arguments section to note that --outdir can be used with --splitting (exception).
• Minor formatting change to the Windows arm64 target line display (strikethrough styling); no functional impact.

Alterations to the declarations of exported or public entities

• No public/exported entity declarations were changed.

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

docs/bundler/index.mdx:
"""

AI-generated summary of changes

• Removed the duplicate "linked" option from the sourcemap union in BuildConfig.sourcemap. The old type allowed "none" | "linked" | "inline" | "external" | "linked" | boolean; the new type allows "none" | "linked" | "inline" | "external" | boolean. This eliminates the redundant literal while preserving the remaining valid values and the boolean shorthand.

Alterations to the declarations of exported or public entities

• Updated: BuildConfig.sourcemap signature in docs/bundler/index.mdx
  • From: sourcemap?: "none" | "linked" | "inline" | "external" | "linked" | boolean; // default: "none", true -> "inline"
  • To: sourcemap?: "none" | "linked" | "inline" | "external" | boolean; // default: "none", true -> "inline"

Estimated code review effort: Medium
"""

---

docs/docs.json:
"""

AI-generated summary of changes

• Added "/pm/cli/info" to the Pages list under the "Publishing & Analysis" group in the "Package Manager" tab.
• Added "/guides/test/concurrent-test-glob" to the Pages list under the "Test Runner" group in the "Guides" tab.

Alterations to the declarations of exported or public entities

• Page list modified: docs/docs.json → In navigation.tabs[0].groups[1].pages (Package Manager, Publishing & Analysis), inserted "/pm/cli/info".
• Page list modified: docs/docs.json → In navigation.tabs[4].groups[2].pages (Guides, Test Runner), inserted "/guides/test/concurrent-test-glob".

Estimated code review effort: Medium
"""

---

docs/guides/test/concurrent-test-glob.mdx:
"""

AI-generated summary of changes

Introduces a new documentation file docs/guides/test/concurrent-test-glob.mdx explaining how to use a concurrentTestGlob option to run tests concurrently based on filename patterns. Includes project structure examples, bunfig.toml configuration, unit and integration test examples (sequential vs. concurrent), running instructions, migration strategy, tips, and guidance for multiple patterns. No code or public API changes are introduced.

Manifest File Analyzer

Estimated code review effort: Low
"""

---

docs/guides/websocket/context.mdx:
"""

AI-generated summary of changes

• Removed the explicit generic type parameter from Bun.serve calls (from Bun.serve<{ socketId: number }>(...) to Bun.serve(...)).
• Introduced and exemplified a per-websocket contextual data typing by adding a data property inside the websocket options:
  • websocket.data is shown as data: {} as { socketId: number } in one snippet.
  • websocket.data is shown as data: {} as WebSocketData in another snippet.
• The per-connection contextual data is then accessed via ws.data.* in message handlers, with the examples updated accordingly.
• Updated examples to show typing the WebSocket data type via a separate WebSocketData type and to reference ws.data in usage.

Alterations to the declarations of exported or public entities

• Method signature updated: Bun.serve usage changed from Bun.serve<{ socketId: number }>(...) to Bun.serve(...) in file docs/guides/websocket/context.mdx.
• Public API addition: websocket option now supports a data property (typing examples shown as:
  • data: {} as { socketId: number }
  • data: {} as WebSocketData
    placed under the websocket configuration) in file docs/guides/websocket/context.mdx.

Estimated code review effort: Medium
"""

---

docs/guides/websocket/pubsub.mdx:
"""

AI-generated summary of changes

• Updated code example to remove the generic type parameter on Bun.serve, changing from Bun.serve<{ username: string }> to Bun.serve({}).
• Added a public configuration property in the websocket section: data: {} as { username: string } to specify the type of ws.data.

Alterations to the declarations of exported or public entities

• Method signature updated: Bun.serve<{ username: string }> → Bun.serve({}) in file docs/guides/websocket/pubsub.mdx
• Property added: data in the websocket configuration object, with type assertion {} as { username: string } in docs/guides/websocket/pubsub.mdx

Estimated code review effort: Medium
"""

---

docs/guides/websocket/simple.mdx:
"""

AI-generated summary of changes

• Removed the specific generic type parameter from the Bun.serve call, changing from Bun.serve<{ authToken: string }>() to Bun.serve().
• In the websocket configuration, added a data property with an explicit type annotation: data: {} as { authToken: string }.
• Added a comment indicating how to specify the ws.data type in TypeScript.

Alterations to the declarations of exported or public entities

• None

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

docs/pm/cli/info.mdx:
"""

AI-generated summary of changes

• Added a new documentation file docs/pm/cli/info.mdx describing the bun info CLI. The doc covers usage (bun info react), viewing specific versions (bun info react@18.0.0), querying specific properties (version, dependencies, repository.url), JSON output (--json), and an alias (bun pm view is equivalent to bun info). Includes examples for basic info, specific versions, listing all versions, dependencies, homepage, and JSON output. No code changes are introduced.

Alterations to the declarations of exported or public entities

Manifest File Analyzer

Estimated code review effort: Low
"""

---

docs/pm/cli/install.mdx:
"""

AI-generated summary of changes

Adds substantial documentation updates for bun install configuration and platform behavior:

• Adds a dedicated environment variables configuration block with a priority note over bunfig.toml and a complete table of BUN_CONFIG_* variables.
• Introduces a new “Configuring with environment variables” section under the existing configuration area.
• Replaces or augments existing bunfig.toml configuration coverage with expanded guidance, including merged results when both bunfig.toml paths exist and explicit examples.
• Adds a new “Configuring with environment variables” block that explains precedence, installation backend selection, cache locations, and path normalization details.
• Introduces a new “Platform-specific dependencies?” subsection detailing how Bun stores and uses CPU/OS values in the lockfile, and how to override target platform using --cpu and --os, along with accepted values.
• Adds a comprehensive “Platform-specific backends” section, including per-backend descriptions and command examples (hardlink, clonefile, clonefile_each_dir, copyfile, symlink) and notes on cross-platform behavior.
• Appends extensive documentation around npm registry metadata, lockfile behavior, and pnpm migration details as part of the broader platform and backend narrative.

Alterations to the declarations of exported or public entities

• None

Manifest File Analyzer

"""

---

docs/pm/cli/link.mdx:
"""

AI-generated summary of changes

Adds an "Unlinking" usage section to the CLI docs, detailing how to run bun unlink in a package directory, with terminal and txt outputs showing the unlink invocation and result. This is a content addition that introduces a new workflow for unregistering a local package; no code logic or control flow changes are present elsewhere in the diff.

Alterations to the declarations of exported or public entities

• No public/exported declarations modified.

Estimated code review effort: Low
"""

---

docs/pm/cli/publish.mdx:
"""

AI-generated summary of changes

• Adds a new CLI flag --tolerate-republish for bun publish. When used, it exits with code 0 even if the package version already exists, enabling easier CI/CD re-runs. Included example usage and placement alongside existing flags, without altering existing behavior of other flags.

• No changes to exported/public declarations detected.

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

docs/pm/workspaces.mdx:
"""

AI-generated summary of changes

• Introduced explicit examples showing glob patterns for workspaces including negative patterns (e.g., !packages//test/, !packages//template/) and updated the supported-glob note to mention negative patterns with a direct link.
• Replaced previous note content with a revised description that includes negative patterns as part of Bun's workspace glob support.
• Added new code blocks illustrating a root package.json with workspaces including negative patterns and a corresponding example for a workspace package (pkg-a) referencing dependencies via workspace:*.
• Expanded the surrounding examples to include a concrete packages/** pattern and exclusions, plus an example package.json for an internal workspace reference.
• Adjusted formatting to include code block metadata (icon="file-json") around the JSON snippets.

Alterations to the declarations of exported or public entities

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

docs/project/contributing.mdx:
"""

AI-generated summary of changes

• Replaced "Install Dependencies" header with "Using Nix (Alternative)" and added a Nix flake-based setup with commands to enter a reproducible environment.
• Introduced "Install Dependencies (Manual)" unchanged in structure but with added dependencies and commands; added sccache to macOS and Ubuntu/Debian blocks.
• Expanded OS-specific dependency blocks to include sccache where applicable.
• Added an optional sccache installation section with platform-specific commands and notes on S3 support and installation method via cargo.
• Added AWS credential guidance for sccache, including detail on logging in with the AWS CLI and environment configuration, plus a details section for common issues.
• Updated debug logging guidance to reflect the new Output.scoped parameter usage (.hidden instead of false) in the relevant example.
• Removed the subsection “ccache conflicts with building TinyCC on macOS.”
• Added sections for registering AWS credentials, common issues for sccache, and related troubleshooting.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Medium

Estimated code review effort: Medium
"""

---

docs/quickstart.mdx:
"""

AI-generated summary of changes

• Replaced the existing scripts block with a structure that adds a top-level private: true property, while keeping the "start" script value unchanged ("bun run index.ts").
• Added a peerDependencies section specifying "typescript": "^5".
• Added a devDependencies entry for "@types/bun": "latest".
• Included code-comment markers around the modified snippet sections (// [!code ++]).

Alterations to the declarations of exported or public entities

• Property added: private (boolean) in the exported public example object package.json within docs/quickstart.mdx
• Property added: peerDependencies object with typescript: "^5" in the exported public example object package.json within docs/quickstart.mdx
• Property added: devDependencies object with "@types/bun": "latest" in the exported public example object package.json within docs/quickstart.mdx

Estimated code review effort: Low

Estimated code review effort: Medium
"""

---

docs/runtime/bunfig.mdx:
"""

AI-generated summary of changes

• Adds comprehensive documentation blocks for new test configuration options under the test section:
  • test.concurrentTestGlob: describes a glob to automatically run matching tests with concurrent execution, with an example bunfig.toml snippet and notes that --concurrent overrides it.
  • test.onlyFailures: documents showing only failed tests in output with default false, plus equivalent CLI flag (--only-failures).
  • test.reporter: introduces nested options:
    • test.reporter.dots: enables a compact dots output, with default false.
    • test.reporter.junit: enables JUnit XML reporting and specifies output file path.
• Repeats the test-related documentation blocks under bunfig.toml, ensuring consistent coverage for concurrentTestGlob, onlyFailures, and reporter settings.
• Updates the description about bunfig.toml loading for bun run:
  • Changes from the previous statement about not always loading bunfig.toml in local projects to a clearer claim that bunfig.toml is only automatically loaded locally, and that a global bunfig.toml is not checked.

This is documentation text changes that introduce multiple new config options and adjust a loading behavior statement. While not code, the changes affect user-facing configuration semantics and wording and may warrant a senior review for accuracy and consistency.

Alterations to the declarations of exported or public entities

• None

Manifest File Analyzer

Estimated code review effort: High
"""

---

docs/runtime/http/routing.mdx:
"""

AI-generated summary of changes

Changed the fetch handler's IP formatting from using the raw ip value to derived ip.address, altering the returned Response string from "Your IP is {ip}" to "Your IP is {ip.address}". This implies requestIP(req) now yields an object with an address property, changing the visible output without modifying control flow or error handling.

Alterations to the declarations of exported or public entities

• None

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

docs/runtime/http/websockets.mdx:
"""

AI-generated summary of changes

• Updates code examples to show server.upgrade(req, { headers: { ... } }) instead of wrapping headers in a nested object, foregrounding the headers object in the upgrade call.
• Adds guidance for strongly typing WebSocket data by suggesting a data property on the websocket handler object, making ws.data available across all lifecycle hooks.
• Introduces two notes clarifying that using a type parameter on Bun.serve (e.g., Bun.serve({...})) was removed due to a TypeScript limitation, in favor of the data property approach, and places these notes in two locations: within the contextual data section and within the Pub/Sub example narrative.

Alterations to the declarations of exported or public entities

• None — no changes to exported/public API declarations.

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

docs/runtime/module-resolution.mdx:
"""

AI-generated summary of changes

Adds a NODE_PATH documentation section detailing how Bun resolves modules using NODE_PATH, including syntax, examples for Unix and Windows delimiters, and integration with package.json exports to determine entrypoints. The additions appear in two places within the module-resolution page, both describing NODE_PATH behavior and example usage, as well as showing how exports are resolved once a package is found.

Alterations to the declarations of exported or public entities

• No exported/public declarations were modified.

Estimated code review effort: High
"""

---

docs/runtime/redis.mdx:
"""

AI-generated summary of changes

• Adds VALKEY_URL as an alternative environment variable for Redis connection info, in addition to REDIS_URL, altering the precedence list by including VALKEY_URL before the default. No other behavior changes.

Alterations to the declarations of exported or public entities

• No public/exported entity declarations were modified.

Estimated code review effort: Medium
"""

---

docs/test/configuration.mdx:
"""

AI-generated summary of changes

• Added documentation sections for test execution configuration under bunfig.toml:
  • concurrentTestGlob: documents running test files matching a glob with concurrent tests, with CLI override via --concurrent.
  • randomize: documents running tests in random order.
  • seed: documents setting a seed for reproducible random order (requires randomize = true).
  • rerunEach: documents re-running each test file multiple times to detect flakiness.
• The new sections include code block examples and behavioral notes, and are inserted in two locations within the file, effectively duplicating the documentation blocks.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Medium
"""

---

docs/test/reporters.mdx:
"""

AI-generated summary of changes

• Added a new Dots Reporter documentation section describing the dots reporter behavior and example usage.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: High
"""

---

packages/bun-types/bun.d.ts:
"""

AI-generated summary of changes

Removed a duplicate option from the public BuildConfigBase.sourcemap type. The allowed union is reduced from "none" | "linked" | "inline" | "external" | "linked" | boolean to "none" | "linked" | "inline" | "external" | boolean. No change to control flow or error handling; only the public type signature for sourcemap is corrected by eliminating the repeated "linked" entry.

• Signature updated: packages/bun-types/bun.d.ts → interface BuildConfigBase:
  • Property: sourcemap
  • Before: sourcemap?: "none" | "linked" | "inline" | "external" | "linked" | boolean;
  • After: sourcemap?: "none" | "linked" | "inline" | "external" | boolean;

Estimated code review effort: High
"""

---

test/bundler/expectBundled.ts:
"""

AI-generated summary of changes

• Cleaned a duplicate literal in the BundlerTestInput.sourceMap type by removing an extra "linked" entry from the union. The observable effect is the same set of allowed values ("inline" | "external" | "linked" | "none"), but without the duplicate.

• Method signature updated: declaration of BundlerTestInput.sourceMap in test/bundler/expectBundled.ts. Previously: sourceMap?: "inline" | "external" | "linked" | "none" | "linked"; Now: sourceMap?: "inline" | "external" | "linked" | "none".

Alterations to the declarations of exported or public entities

• Method signature updated: sourceMap field in interface BundlerTestInput within test/bundler/expectBundled.ts (exported/public interface). Before: sourceMap?: "inline" | "external" | "linked" | "none" | "linked"; After: sourceMap?: "inline" | "external" | "linked" | "none".

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

docs/guides/html-rewriter/extract-links.mdx:
"""

AI-generated summary of changes

The changes modify only formatting and inline comments within a code example that converts relative URLs to absolute URLs. No functional behavior or control flow is altered; the try-catch block structure remains the same, with minor repositioning of inline comments and a slight adjustment to the trailing comments on lines within the block.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: High
"""

---

docs/guides/http/file-uploads.mdx:
"""

AI-generated summary of changes

• Added prettier-ignore block markers in code block.
• In the /action handler, now parses formData from the request and extracts name and profilePicture.
• Added validation: if profilePicture is missing, throws an error.
• Writes the uploaded profilePicture to disk as profilePicture.png using Bun.write.
• Returns "Success" upon completing the write operation.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Medium
"""

---

docs/guides/install/add-peer.mdx:
"""

AI-generated summary of changes

• Minor formatting and inline comment adjustments in the JSON example: added a prettier-ignore line before the JSON block, and moved the // [!code ++] markers so that the "@types/bun" entry in peerDependenciesMeta uses an inline comment on the same line as the key, with the "optional": true property also annotated on the same line. No changes to actual data values or logic; only presentation within the code sample.

Alterations to the declarations of exported or public entities

• No changes to exported or public declarations.

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

docs/guides/runtime/define-constant.mdx:
"""

AI-generated summary of changes

• In two code examples within the markdown, added an inline code marker comment // [!code ++] on the same line as the condition or block header.
• Surrounds the updated code blocks with prettier-ignore comments before the code fence.
• No changes to runtime logic or behavior; only formatting/annotation of code samples.

Alterations to the declarations of exported or public entities

• None

Manifest File Analyzer

Estimated code review effort: Low
"""

---

docs/guides/test/spy-on.mdx:
"""

AI-generated summary of changes

• Added a prettier-ignore marker before the code example block.
• Minor formatting adjustment: test declaration now includes an inline comment on the same line as the function.
• Expanded test body by adding an assertion to verify the spy mock calls equals [["pizza"]].
• Updated closing brace line to carry an inline comment corresponding to the added assertion.

Alterations to the declarations of exported or public entities

• No changes to exported/public entity signatures.

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

docs/pm/overrides.mdx:
"""

AI-generated summary of changes

• Minor formatting adjustments in code blocks for overrides/resolutions in docs/pm/overrides.mdx:
  • Move inline code-comment markers from separate lines into the opening line of the overrides/resolutions blocks (e.g., "overrides": { // [!code ++]).
  • Add prettier-ignore blocks before JSON code blocks to suppress formatting changes.
  • Apply identical formatting adjustments to both the "overrides" and "resolutions" examples across the document.
• No changes to logic, behavior, or error handling; only presentation/whitespace changes in code examples.

Alterations to the declarations of exported or public entities

• none

Manifest File Analyzer

Estimated code review effort: Low
"""

---

docs/runtime/html-rewriter.mdx:
"""

AI-generated summary of changes

• The HTMLRewriter example diff in docs/runtime/html-rewriter.mdx is reformatted from a compact, multi-line inline block with code-style diff comments to a line-oriented presentation. The original lines combining multiple images and YouTube blocks are replaced with individual lines for each and each block, using HTML-style comments () and surrounding wrappers, while preserving the overall content and semantics. No functional logic, error handling, or control flow changes; only presentation of the example output is updated.

Alterations to the declarations of exported or public entities

• No changes to exported/public entity declarations.

Estimated code review effort: Low
"""

---

CONTRIBUTING.md:
"""

AI-generated summary of changes

• Fixed a typographical error in the debug logs instruction: corrected "lgos" to "logs" and preserved the surrounding guidance. No changes to control flow or error handling; only text content in the same paragraph.

Alterations to the declarations of exported or public entities

• None

Manifest File Analyzer

Estimated code review effort: Low
"""

---

docs/guides/runtime/cicd.mdx:
"""

AI-generated summary of changes

• Replaces inline code-block end markers from // [!code ++] to # [!code ++] in YAML examples.
• Converts run commands to use # [!code ++] comments instead of // [!code ++].
• Updates the with: section comments from // [!code ++] to # [!code ++], including adding a trailing # [!code ++] to the bun-version line.

Alterations to the declarations of exported or public entities

• None

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

docs/runtime/utils.mdx:
"""

AI-generated summary of changes

Documentation update: the example for overriding the editor in bunfig.toml has been changed from a TOML block using inline // code markers and line comments to a version using # comments and a different comment placement. No functional or behavioral changes; only the documentation snippet formatting.

Alterations to the declarations of exported or public entities

• (no changes)

Estimated code review effort: Low
"""

👤 Suggested Assignees

• robobun
• Jarred-Sumner
• dylan-conway
• RiskyMH

---

🧪 Issue enrichment is currently in early access.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

[github-actions]

Found 3 possible duplicate issues:

1. Bun fails installing correct platform binary #20472
2. Cannot install optional dependencies during dockerization. #12620
3. sharp 33-34 isn't working #21610

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[iajaysharma]

My issue is in version 1.3.4

[SpeedySH]

y, 1.3.4 brokes all that uses fetch

[g00dv1n]

+1, faced the same issue. It works fine on 1.3.3, so just downgraded for now.