bun --bun run build hangs with NextJS 14.1 about bun HOT 8 CLOSED

Thanks for reporting this, digging into this, it looks like Bun has a bug with process.send().

This is the minimal repro that works in Node.js, but fails in Bun:

process.on("message", (data) => {
  console.log("Received:", data);
});

if (!process.env.CHILD) {
  const child_process = require("child_process");

  const subprocess = child_process.spawn(
    process.argv0,
    [__filename],
    {
      stdio: ["inherit", "inherit", "inherit", "ipc"],
      env: {
        ...process.env,
        CHILD: "1",
      },
      serialization: "json",
    },
  );

  subprocess.on("spawn", () => {
    const data = {
      fn: () => {},
      toJSON: () => "toJSON",
    };
    subprocess.send(data, (err) => {
      console.log("Sent:", data, err);
    });
  });
}

from bun.

Face the same issue. Build with bun --bun run build will never succeed. See the detail.

from bun.

I can confirm that this is still valid with Bun v1.0.29.

from bun.

I can confirm this in docker build. My Dockerfile looks like

FROM oven/bun:alpine as builder
WORKDIR /app
COPY package.json bun.lockb ./
RUN bun install --frozen-lockfile
ENV NODE_ENV production
COPY ./ ./
RUN bun --bun run build

FROM oven/bun:alpine as production
WORKDIR /app
ENV NODE_ENV production
COPY --from=builder /app/package.json package.json
COPY --from=builder /app/bun.lockb bun.lockb
RUN bun install --production --frozen-lockfile
COPY --from=builder /app/.next .next
COPY --from=builder /app/public public
COPY --from=builder /app/next.config.mjs next.config.mjs
EXPOSE 3000
ENTRYPOINT ["bun"]
CMD ["--bun", "run", "start"]

The bun version in oven/bun:alpine is v1.0.29.

But it works well on my Mac M1 with the same bun version.

from bun.

Is still happen with Bun v1.0.30.

from bun.

Update to v1.0.33 but still stuck

from bun.

Doing NODE_ENV=production bun run build also causes a similar issue if you do not have development tools installed on Fedora. The same behaviour is replicated the moment --bun comes into play. When running without --bun it looked like a dependency was missing/project dependencies weren't able to be built, causing it to hang - wonder if it could be a similar issue when involving --bun?

from bun.

Also having this issue running bun --bun run next build

from bun.