Lockfile changes when running bun install --frozen-lockfile on pruned repo.

[rtman]

Verify canary release

• [] I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue

Private repository, I have shared the bun lock files with turborepo however.

Which canary version will you have in your reproduction?

2.6.1, the 2.6.2 canary versions are not published to npm yet.

Environment information

#10 0.183 turbo 2.6.1
#10 0.183 
#10 0.199 CLI:
#10 0.199    Version: 2.6.1
#10 0.199    Path to executable: /root/.bun/install/global/node_modules/turbo-linux-arm64/bin/turbo
#10 0.199    Daemon status: Not running
#10 0.199    Package manager: Not found
#10 0.199 
#10 0.199 Platform:
#10 0.199    Architecture: aarch64
#10 0.199    Operating system: linux
#10 0.199    WSL: false
#10 0.199    Available memory (MB): 6966
#10 0.199    Available CPU cores: 14
#10 0.199 
#10 0.199 Environment:
#10 0.199    CI: None
#10 0.199    Terminal (TERM): unknown
#10 0.199    Terminal program (TERM_PROGRAM): unknown
#10 0.199    Terminal program version (TERM_PROGRAM_VERSION): unknown
#10 0.199    Shell (SHELL): unknown
#10 0.199    stdin: false
#10 0.199

Expected behavior

Expecting bun install --frozen-lockfile --linker hoisted: to complete successfully and not encounter a change in the lockfile causing an error.

Actual behavior

 => [pruner 2/2] RUN turbo prune @repo/member-app-web --docker                                                                               2.7s 
 => [installer 2/4] COPY --from=pruner /usr/src/app/out/json/ .                                                                              0.0s 
 => [installer 3/4] COPY --from=pruner /usr/src/app/out/bun.lock ./bun.lock                                                                  0.0s 
 => ERROR [installer 4/4] RUN bun install --frozen-lockfile --linker hoisted                                                                 1.8s 
 => [builder 2/6] COPY --from=pruner /usr/src/app/out/full/ .                                                                                0.2s 
------                                                                                                                                            
 > [installer 4/4] RUN bun install --frozen-lockfile --linker hoisted:                                                                            
0.100 bun install v1.3.3 (274e01c7)                                                                                                               
0.114 Resolving dependencies                                                                                                                      
1.721 Resolved, downloaded and extracted [313]                                                                                                    
1.725 error: lockfile had changes, but lockfile is frozen                                                                                         
1.725 note: try re-running without --frozen-lockfile and commit the updated lockfile
------
Dockerfile:18
--------------------
  16 |     COPY --from=pruner /usr/src/app/out/json/ .
  17 |     COPY --from=pruner /usr/src/app/out/bun.lock ./bun.lock
  18 | >>> RUN bun install --frozen-lockfile --linker hoisted
  19 |     # RUN bun install --linker hoisted
  20 |     
--------------------
ERROR: failed to build: failed to solve: process "/bin/sh -c bun install --frozen-lockfile --linker hoisted" did not complete successfully: exit code: 1

To Reproduce

I've provided the bun.lock from the pruned repo and the original repo via email to @anthonyshew

Additional context

Note I was unable to install the latest canary, 2.6.2-canary-1 or 0, as they are not available on npm yet. This looks to be similar to #11007

[krzkz94]

Having a similar issue, the "nested dependencies fix" that was supposedly published in 2.6.1 doesn't work.

 => CACHED [pruner 3/3] RUN turbo prune @ex/api --docker                                       0.0s
 => CACHED [builder 1/4] COPY --from=pruner /app/out/json/ .                                   0.0s
 => CACHED [builder 2/4] COPY --from=pruner /app/out/bun.lock ./bun.lock

 > [builder 3/4] RUN bun install --frozen-lockfile:
0.109 bun install v1.3.3 (274e01c7)
0.173 570 |     "@trigger.dev/core": ["@trigger.dev/core@4.1.0", "", { "dependencies": { "@bugsn
0.173           ^
0.173 error: Failed to resolve prod dependency 'nanoid' for package '@trigger.dev/core'
0.173     at bun.lock:570:5
0.173 InvalidPackageInfo: failed to parse lockfile: 'bun.lock'
0.173 
0.173 warn: Ignoring lockfile
0.173 error: lockfile had changes, but lockfile is frozen

[preampinbut]

I'm also having this have use the og bun.lock ro fix this
I check into the generated bun.lock many dependencies got removed some have version changed cause bun to have a stroke

COPY --from=prune --exclude=bun.lock /app/out/json/ .
COPY bun.lock ./bun.lock

[rtman]

@anthonyshew Do you (or your team) have any time to look at this? It's blocking for my team migrating to turbo.

Maintainer's note

Please do not spam issues with any of:

• Requests for updates
  • When maintainers have updates to share, they post them. They do not wait for someone to ask for an update to do so.
• "+1" comments or similar that do not add any debugging information
  • If you want to express your interest in an issue, add a 👍 emoji to the original issue report.

Comments on GitHub Issues produce notifications for anyone participating on the issue, adding noise but no signal. Please consider contributing a pull request, adding a reproduction, or adding other novel information to the issue if you would like to aid in the Issue being closed.

[samishal1998]

It's also affecting our team, I had to remove pruning temporarily (but the image size is huge and CI takes forever)
In my case, I need to lock the version for certain deps, and if i don't use --frozen-lockfile the version will end up changing.

[anthonyshew]

Is everyone here using node-linker: hoisted or --linker hoisted?

[Palid]

I have linker = "isolated", but it seems that linker issues do not matter with pruner. For pruning I just gave up on ci installs.
Already got this to fix on my todolist for dayjob, but it might take a while - there's a few higher priority things to work on first.

[anthonyshew]

The linker configuration matters quite a bit, but interesting to hear that you're getting problems with linker = "isolated".

For anyone on this issue, I will only be able to work with complete reproductions to ensure your case is resolved. @rtman, I will try to work with your lockfile now but its possible a complete reproduction may be needed now that the lockfile parser is more matured out and we're getting out to the configuration edges.