bun-pkg-why-is-node-running-2.3.0
checks.aarch64-darwin.evidence-worker
· build #1301
· raw
1stibnite: building bmsq9vyir35dxnjq8wnd88aagx0ply07-bun-pkg-why-is-node-running-2.3.0.drv
patchPhase
2patching script interpreter paths in /nix/store/zmvx9zsy5r35qsqhgkwzjvwnpibpmydk-bun-pkg-why-is-node-running-2.3.0/share/bun-packages3/nix/store/zmvx9zsy5r35qsqhgkwzjvwnpibpmydk-bun-pkg-why-is-node-running-2.3.0/share/bun-packages/why-is-node-running@2.3.0/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/swv533ka4blhhr1i32imipwxyikmyps5-bun-with-fake-node/bin/node"cacheEntryPhase
4info: Creating entry for `why-is-node-running@2.3.0`...56debug: Link out path: `/nix/store/zmvx9zsy5r35qsqhgkwzjvwnpibpmydk-bun-pkg-why-is-node-running-2.3.0/share/bun-cache/why-is-node-running@2.3.0@@@1`.78debug: Link parent dir: `/nix/store/zmvx9zsy5r35qsqhgkwzjvwnpibpmydk-bun-pkg-why-is-node-running-2.3.0/share/bun-cache`.910debug: Created parent directory.1112info: Successfully created cache entry symlink for `why-is-node-running@2.3.0`.13