Support `prune` in Bun workspaces #7456

I am also very interested in this being supported. My team would love to use bun alongside turbo but this is the main bottleneck preventing us from doing so.

0 replies

JarvisPrestidge · 2024-08-27T23:02:18Z

JarvisPrestidge
Aug 27, 2024

For anyone looking for make this "work" in the run up to Bun adding their new JSON lock files (when turbo will add support) hopefully in Q3, you can use this approach.

ARG BUN_VERSION=1.1.26

ARG YARN_PKG_MANAGER="this.packageManager=\"yarn@1.22.22\""
ARG BUN_PKG_MANAGER="this.packageManager=\"bun@${BUN_VERSION}\""

FROM oven/bun:${BUN_VERSION} as bun
WORKDIR /app

FROM oven/bun:${BUN_VERSION}-alpine as bun-alpine
WORKDIR /app

# ================= TURBO PRUNE ===================

FROM bun as pruned
ARG YARN_PKG_MANAGER
COPY . .
RUN bunx json -I -f package.json -e ${YARN_PKG_MANAGER}
RUN bunx turbo prune --scope="example-service" --docker

# =============== INSTALL & BUILD =================

FROM bun as builder
ARG BUN_PKG_MANAGER
COPY --from=pruned /app/out/full/ .
RUN bunx json -I -f package.json -e ${BUN_PKG_MANAGER}
RUN bun install --production
RUN bunx clean-modules -y "**/*.ts" "**/@types/**"
RUN bunx turbo build --filter="example-service..."

# ================== RELEASE ======================

FROM bun-alpine AS release
USER bun
COPY --from=builder /app .
EXPOSE 3000/tcp
WORKDIR /app/apps/example-service
ENTRYPOINT [ "bun", "dist/main.js" ]

This is for a Nest.js monorepo with internal packages that aren't compiled.

The build script in the example-service simply uses bun build as the "bundler" with "packages": "external" set.

p.s. I needed to run bun install against the "full" output of prune because one of my monorepo packages is a cli binary that i need linked into node_modules/.bin but if you don't have that requirement you can follow the standard, copy over out/json, bun install, copy over out/full then build.

2 replies

Lanhild Mar 11, 2025

For anyone looking for make this "work" in the run up to Bun adding their new JSON lock files (when turbo will add support) hopefully in Q3, you can use this approach.

This doesn't seem to work on my side, I still get the Cannot prune without parsed lockfile error.

Lanhild Mar 15, 2025

For anyone @ here, I've solved the issue on my side by using an earlier version of bun@1.1.29 and turbo@2.3.4

camero2734 · 2025-03-15T17:02:09Z

camero2734
Mar 15, 2025

I've taken a stab at implementation here: #10175

0 replies

baptisteArno · 2024-01-31T16:53:28Z

baptisteArno
Jan 31, 2024

YES please 🙏

0 replies

jukkamarttinen · 2024-02-27T22:15:36Z

jukkamarttinen
Feb 27, 2024

This would be lot appreciated for us too.

0 replies

jarvis394 · 2025-03-06T00:35:29Z

jarvis394
Mar 6, 2025

https://bun.sh/blog/bun-v1.1.39#bun-lock-is-bun-s-new-text-based-lockfile

In this release, we've added a new human-readable lockfile format: bun.lock. This makes git diffs and merge conflicts work better, and unblocks tooling like Dependabot, Renovate, Turbo prune, and more.

Really hoping to see an update on this 🚢

0 replies

thecrabcode · 2024-01-16T09:59:56Z

thecrabcode
Jan 16, 2024

Is there any update on this guys? We would also like to use Turborepo alongside bun, but this issue is quite important for us. I'd be happy to help in any way I can

0 replies

baptisteArno · 2025-03-06T14:32:14Z

baptisteArno
Mar 6, 2025

Maybe Devin can do this? 🧌

0 replies

terion-name · 2024-06-28T13:28:41Z

terion-name
Jun 28, 2024

Bun supports yarn.lock for very long time. It is a shame that it is not supported in turbo =(

0 replies

jordanebelanger · 2023-10-03T16:42:30Z

jordanebelanger
Oct 3, 2023

Note that the output pruned repository must use the package manager you select (yarn or pnpm)—it cannot use bun.

Doesn't bun support the yarn lockfile format? Why the need to switch package manager even after converting a bun.lockb to a yarn lockfile?

P.S would love for this issue to get attention, this is the last blocker for us to move over to bun as our package manager.

0 replies

lmyslinski · 2025-10-20T14:27:31Z

lmyslinski
Oct 20, 2025

I can confirm that using turbo@canary has fixed my issues.

❯ docker build . --progress=plain -t "paperjet"
#0 building with "orbstack" instance using docker driver

#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 1.75kB done
#1 DONE 0.0s

#2 [internal] load metadata for docker.io/oven/bun:1.3.0
#2 DONE 0.2s

#3 [internal] load .dockerignore
#3 transferring context: 733B done
#3 DONE 0.0s

#4 [base 1/3] FROM docker.io/oven/bun:1.3.0@sha256:00cccad6e9c66bbacc250851f689168606aaea551ac473e908bbcf00a5645025
#4 DONE 0.0s

#5 [base 2/3] WORKDIR /usr/src/app
#5 CACHED

#6 [installer 1/4] WORKDIR /usr/src/app
#6 CACHED

#7 [base 3/3] RUN --mount=type=cache,target=/root/.bun/install/cache     bun install -g turbo@2.5.9-canary.8
#7 CACHED

#8 [internal] load build context
#8 transferring context: 2.92MB 5.1s
#8 transferring context: 3.85MB 5.5s done
#8 DONE 5.6s

#9 [pruner 1/2] COPY . .
#9 DONE 9.8s

#10 [pruner 2/2] RUN turbo prune @paperjet/api @paperjet/dashboard --docker
#10 0.321  WARNING  No locally installed `turbo` found in your repository. Using globally installed version (2.5.9-canary.8), which can cause unexpected behavior.
#10 0.321
#10 0.321 Installing the version in your repository (2.5.9-canary.8) before calling `turbo` will result in more predictable behavior across environments.
#10 0.326
#10 0.326 Attention:
#10 0.326 Turborepo now collects completely anonymous telemetry regarding usage.
#10 0.326 This information is used to shape the Turborepo roadmap and prioritize features.
#10 0.326 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
#10 0.326 https://turborepo.com/docs/telemetry
#10 0.326
#10 0.327 turbo 2.5.9-canary.8
#10 0.327
#10 0.390 Generating pruned monorepo for @paperjet/api, @paperjet/dashboard in /usr/src/app/out
#10 0.418  - Added @paperjet/api
#10 0.428  - Added @paperjet/auth
#10 0.770  - Added @paperjet/dashboard
#10 0.801  - Added @paperjet/db
#10 0.809  - Added @paperjet/email
#10 0.822  - Added @paperjet/engine
#10 0.844  - Added @paperjet/queue
#10 0.850  - Added @paperjet/shared
#10 0.850  - Added @paperjet/tsconfig
#10 DONE 1.6s

#11 [installer 2/4] COPY --from=pruner /usr/src/app/out/json/ .
#11 DONE 0.1s

#12 [builder 2/4] COPY --from=pruner /usr/src/app/out/full/ .
#12 ...

#13 [installer 3/4] COPY --from=pruner /usr/src/app/out/bun.lock ./bun.lock
#13 DONE 0.1s

#14 [installer 4/4] RUN --mount=type=cache,target=/root/.bun/install/cache     bun install
#14 0.094 bun install v1.3.0 (b0a6feca)
#14 ...

#12 [builder 2/4] COPY --from=pruner /usr/src/app/out/full/ .
#12 DONE 4.0s

#14 [installer 4/4] RUN --mount=type=cache,target=/root/.bun/install/cache     bun install

See https://github.com/MLNativeAI/paperjet/ for reference.

0 replies

apex-woot · 2024-07-24T11:56:30Z

apex-woot
Jul 24, 2024

+1
It would be great to have bun support prune in any form to be able to use turbo prune!

0 replies

wladpaiva · 2023-12-01T23:17:10Z

wladpaiva
Dec 1, 2023

Bun supports a human readable lock file now
https://bun.sh/guides/install/yarnlock

Maybe an easy fix would be to have an option for turbo to read specific lock files the same way bun does
turbo prune --yarn

1 reply

jukkamarttinen Feb 27, 2024

This would be the best option, if possible.

chris-olszewski · 2023-10-03T23:19:21Z

chris-olszewski
Oct 3, 2023

Bun supports serializing the bun.lockb to a yarn.lock to make it human readable, but it doesn't support using parsing a yarn.lock or creating a bun.lockb from a yarn.lock.

There's some chatter around bun getting support for using a package-lock.json and that could open a path forward to turbo prune supporting bun.

0 replies

eduardofischer · 2025-03-11T14:58:00Z

eduardofischer
Mar 11, 2025

We're also looking forward to this 🙂

0 replies

Andy-d-g · 2025-10-16T09:01:38Z

Andy-d-g
Oct 16, 2025

1 reply

anthonyshew Oct 18, 2025
Maintainer

The tracking issue is right above this comment. 😄

The most recent canaries of Turborepo have a fix for the new Bun lockfile version. Please open an issue with a reproduction if you run into issues.

frixou89 · 2025-10-25T07:26:39Z

frixou89
Oct 25, 2025

This worked for me.

bun install --linker hoisted without --frozen-lockfile flag

FROM oven/bun:1.3.1-alpine AS base
 
FROM base AS builder
WORKDIR /app
RUN bun install --global turbo@^2
COPY . .
 
RUN turbo prune api --docker
 
FROM base AS installer
WORKDIR /app
 
COPY --from=builder /app/out/json/ .
RUN bun install --linker hoisted
 
COPY --from=builder /app/out/full/ .
RUN bun run turbo build
 
FROM base AS runner
WORKDIR /app
 
COPY --from=installer /app/apps/api/dist .

EXPOSE 3000

ENTRYPOINT ["./app"]

0 replies

cjkihl · 2025-03-15T10:01:40Z

cjkihl
Mar 15, 2025

Any updates?

0 replies

maximblack · 2024-07-24T12:02:38Z

maximblack
Jul 24, 2024

as a workaround, I am using pnpm as a package manager (for pruning), then running the release with bun

# use the official Bun image
# see all versions at https://hub.docker.com/r/oven/bun/tags
FROM oven/bun:1 AS base
WORKDIR /app

FROM node:20-alpine AS pruned
ARG PROJECT=@t4/api
WORKDIR /app

COPY . .
RUN npx turbo prune --scope=${PROJECT} --docker
COPY tsconfig.json ./out/full/

# install dependencies into temp directory
# this will cache them and speed up future builds
FROM node:20-alpine AS deps
ARG CI=true

# Setup pnpm environment
ENV PNPM_HOME="/pnpm"
ENV PATH="$PNPM_HOME:$PATH"
RUN corepack enable
RUN corepack prepare pnpm@latest --activate


RUN mkdir -p /temp/dev
COPY --from=pruned /app/out/json/ /temp/dev/
RUN cd /temp/dev && pnpm install --frozen-lockfile --prefer-frozen-lockfile

# install with --production (exclude devDependencies)
RUN mkdir -p /temp/prod
COPY --from=pruned /app/out/json/ /temp/prod/
RUN cd /temp/prod && pnpm install --prod --frozen-lockfile --prefer-frozen-lockfile

# copy node_modules from temp directory
# then copy all (non-ignored) project files into the image
FROM node:20-alpine AS prerelease
# Setup pnpm environment
ENV PNPM_HOME="/pnpm"
ENV PATH="$PNPM_HOME:$PATH"
RUN corepack enable
RUN corepack prepare pnpm@latest --activate


WORKDIR /app
COPY --from=deps /temp/dev .
COPY --from=pruned /app/out/full/ .

# [optional] tests & build
ENV NODE_ENV=production
RUN cd packages/api && pnpm run zenstack:generate
# RUN bun test
# RUN bun run build
# RUN bun run turbo build --filter=@t4/api

# copy production dependencies and source code into final image
FROM base AS release
WORKDIR /app
COPY --from=deps /temp/prod .
COPY --from=prerelease /app .
# COPY --from=prerelease /app/node_modules/.pnpm/@prisma+client* ./node_modules/.pnpm/
COPY --from=prerelease /app/node_modules/.pnpm/@prisma+client* ./node_modules/.pnpm/@prisma+client@5.17.0_prisma@5.17.0

# run the app
USER bun
EXPOSE 8787/tcp

#HEALTHCHECK --interval=30s --timeout=30s --start-period=5s --retries=3 CMD [ "wget", "-q0", "http://localhost:8787/health" ]
ENTRYPOINT [ "bun", "run", "packages/api/src/worker.ts" ]
#ENTRYPOINT [ "bash" ]

0 replies

nathanhammond · 2023-09-20T05:28:25Z

nathanhammond
Sep 20, 2023

We're aware of this limitation. Serializing to the binary Bun lockfile format is a non-trivial task and not imminently forthcoming.

For now, if you want to use turbo prune for a Bun project, you can losslessly use it with either yarn or pnpm. We recommend choosing yarn because the node_modules layout is most-similar to Bun and it is more-likely to be compatible with your project.

cd ./path/to/bun/project
bunx @turbo/workspaces@latest convert ./ yarn --skip-install
turbo prune

If you don't want any of the automated changes to be permanent you can then proceed to revert all changes in the repository.

Note that the output pruned repository must use the package manager you select (yarn or pnpm)—it cannot use bun.

0 replies

skeie · 2025-03-17T08:26:43Z

skeie
Mar 17, 2025

This will be awesome!

0 replies

XenoWad01 · 2024-03-02T18:34:32Z

XenoWad01
Mar 2, 2024

I am unsure if this actually fixed the problem as I didnt have time to test that the lock file works. But what seemed to have worked for me was doing turbo prune --scope=@bookd/bookd-api --docker; exit 0 which basically ignores the error alltogether. Im not sure if it works properly or not but it does generate an out/ folder properly. It does generate an out folder but I suspect it just contains the non pruned version of the lock file. Here is my docker file for reference:

FROM node:20.11.0 AS init


# RUN npm install -g unzip
RUN npm install -g bun

RUN bun upgrade --canary

RUN npm install -g synp
RUN npm install -g turbo@1.12.3


WORKDIR /usr/src/app
COPY . .

RUN turbo prune --scope=@bookd/bookd-api --docker; exit 0

FROM init AS installer

WORKDIR /usr/src/app


COPY --chown=node .gitignore .gitignore
COPY --from=init --chown=node /usr/src/app/out/json/ ./



COPY --from=init --chown=node /usr/src/app/out/full/ ./

RUN rm -rf /usr/src/app/out/
RUN bun install --frozen-lockfile --production
RUN bun run build

ENV PORT=4000

EXPOSE $PORT

WORKDIR /usr/src/app/packages/bookd-api

RUN chown node /usr/src/app/* && chmod 755 /usr/src/app/*

USER node
CMD bun run /usr/src/app/packages/bookd-api/app.ts

(Dont mind the npm stuf it seems bun install -g does not really work inside docker for me because the it doesent seem to add the commands to path inside docker only)

From what I understand the reason for this not being supported is that prune actually generates a new lockfile from the old one with only a certain package's dependencies in it and it cannot currently parse the .lockb format. Bun currently supports installing from lockb (and from package-lock.json if you are on canary as of this moment). Here is the open issue related to it supporting yarn.lock file: oven-sh/bun#6409. As soon as they support installing from a yarn.lock file this should become a non problem because bun install can generate a yarn.lock file with bun install -y or adding [install.lockfile] print = "yarn" to your bunfig.toml file at the root of your project. In theory you could also use https://github.com/imsnif/synp for converting the yarn.lock file to a package-lock.json file. Turbo seems to auto-detect the type of lockfile you have and will whine about you having multiple ones. What could fix this is a argument for turbo or turbo prune to specify the exact lockfile to use (as mentioned here #7456 (comment)). The current workaround proposed by me is that you just delete the lock files you dont need inside docker.

TLDR:

(be on bun canary) => install with bun install -y always or add the [install.lockfile] print = "yarn" to your bunfig.toml file => (inside docker) => install synp => delete .lockb file => convert yarn.lock to package-lock.json with snyp => remove old yarn.lock => you currently have a package-lock.json and if you are on canary you can install from it with bun.

I didnt yet have time to fully test this theory but if someone has time and manages to do so please let me know I would appreciate it alot. Otherwise I will try to come back to you when I properly pull this off ( which will take some time as I am new to docker and devops in general ).

0 replies

Support prune in Bun workspaces #7456

Uh oh!

Which project is this feature idea for?

Describe the feature you'd like to request

Describe the solution you'd like

Describe alternatives you've considered

Replies: 36 comments · 44 replies

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

anthonyshew Mar 20, 2025 Maintainer

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

anthonyshew Oct 18, 2025 Maintainer

Uh oh!

Uh oh!

Support `prune` in Bun workspaces #7456

Replies: 36 comments 44 replies

anthonyshew
Mar 20, 2025
Maintainer

anthonyshew Oct 18, 2025
Maintainer