Repository navigation
Bun top-level patchedDependencies is not applied when installing from bun.lock
#722
SummaryWhen a project uses Bun's top-level The aube config docs show patch support through Reprogit clone https://github.com/mwolson/tmp-aube-issues.git
cd tmp-aube-issues/bun-patched-dependencies
./repro.shIf BUN_BIN=/path/to/real/bun ./repro.shExpectedBoth native Bun and aube install ActualNative Bun applies the patch. Aube installs successfully, but the package remains unpatched: This showed up in a real Bun project as a missing patched export from |
Replies: 1 comment 1 reply
|
Thanks for the clear repro. I tracked this down to install-time patch loading only reading I opened #724 to fix it. That PR reads Bun top-level This comment was generated by Codex. |
Thanks for the clear repro. I tracked this down to install-time patch loading only reading
pnpm.patchedDependencies,aube.patchedDependencies, and workspace-yaml entries from the manifest side. The Bun lockfile parser preserved the top-levelpatchedDependencies, but the linker never saw Bun-onlypackage.json#patchedDependenciesdeclarations.I opened #724 to fix it. That PR reads Bun top-level
patchedDependencies, keeps the existing precedence (bun<pnpm/aube< workspace yaml), and adds both unit coverage and an install-level Bun fixture regression. I also ran your linked repro against the local debug build and it passes with the patch.This comment was generated by Codex.