bun + turbo prune generate different bun.lock files, making bun i --frozen-lockfile not work #11007
Description
Verify canary release
- I verified that the issue exists in the latest Turborepo canary release.
Link to code that reproduces this issue
I can't, it's a private repo.
Which canary version will you have in your reproduction?
2.5.9-canary.10
Environment information
CLI:
Version: 2.5.9-canary.10
Path to executable: XXXXX/node_modules/.bun/turbo-darwin-arm64@2.5.9-canary.10/node_modules/turbo-darwin-arm64/bin/turbo
Daemon status: Not running
Package manager: bun
Platform:
Architecture: aarch64
Operating system: macos
WSL: false
Available memory (MB): 23130
Available CPU cores: 12
Environment:
CI: None
Terminal (TERM): xterm-256color
Terminal program (TERM_PROGRAM): unknown
Terminal program version (TERM_PROGRAM_VERSION): unknown
Shell (SHELL): /bin/zsh
stdin: false
Expected behavior
Thanks for the work on Turborepo !
The expected behavior is : generate the same bun lockfile to be able to use --frozen-lockfile
Actual behavior
Here's the original lock file :
{
"lockfileVersion": 1,
"workspaces": {
"": {
"name": "ynov-monorepo",
"devDependencies": {
"@biomejs/biome": "^2.2.2",
"@turbo/gen": "^2.5.0",
"husky": "^8.0.0",
"tailwindcss": "^4.1.12",
"turbo": "^2.5.9-canary.10",
"typescript": "^5",
},
},
// ...
}
Here's the lock file after prunning.
"workspaces": {
"": {
"name": "ynov-monorepo",
"devDependencies": {
"@biomejs/biome": "^2.2.2",
"@turbo/gen": "^2.5.0",
"husky": "^8.0.0",
"tailwindcss": "^4.1.12",
"turbo": "^2.5.9-canary.10",
"typescript": "^5" // <--- missing comma
} // <--- missing comma
},
// ...
}
To Reproduce
Bun 1.3 + Turborepo 2.5.9-canary.10 + Docker.
Additional context
No response