A native dependency refuses to install
sharp, bcrypt, canvas and similar libraries ship Node-ABI prebuilds, and Bun needs either a compatible binary or a working toolchain inside the image to build from source.
Correct image, prebuild resolved
Running on Bun?
Bun is fast when it works, and genuinely strange when it does not. A package that installed under npm fails to postinstall, a Node API returns a slightly different shape, or a native addon refuses to load inside a Docker image built on the wrong base. We trace the gap between Node and Bun, and pick the smallest fix that keeps you productive.
What it is
Bun is a JavaScript runtime, package manager, bundler and test runner, released publicly by Jarred Sumner and Oven in 2022 and reaching version 1.0 in September 2023. Unlike Node and Deno, which build on Google's V8, Bun uses Apple's JavaScriptCore engine and is written largely in Zig, with a focus on raw startup time and throughput.
It implements a growing subset of Node compatibility: most of node:fs, node:path, node:crypto and node:http work out of the box, along with npm-style package resolution and a drop-in replacement for the npm, yarn and pnpm clients. Bun also ships its own HTTP server, SQLite binding, shell, test runner and build tool, which means a project can often run with no other tooling installed.
The honest version
No technology is all upside. This is where Bun earns its place and where it tends to cause trouble.
Sound familiar?
The Bun problems that bring people to us, and what you have once each one is fixed.
sharp, bcrypt, canvas and similar libraries ship Node-ABI prebuilds, and Bun needs either a compatible binary or a working toolchain inside the image to build from source.
Correct image, prebuild resolved
A library reaches for node:vm, cluster or a specific crypto primitive that Bun has not shipped, and the call throws from deep inside a dependency tree.
Shim, swap, or stay on Node for that path
A bun.lockb written on one version is being read by an older or newer one, or the lockfile was edited by a merge that bun did not resolve cleanly.
Lockfile regenerated, install deterministic
A particular combination of flags, a FFI call, or an unusual file produces a hard crash in the runtime. Reproducing it is the first half of the fix.
Minimal repro filed, worked around
Bun's security default blocks postinstall scripts unless the package is listed in trustedDependencies, which catches packages that legitimately need a build step.
Trusted list explicit, builds running
Concurrent writers against the same file without the right journal mode, or a WAL file left behind by a previous version, produce malformed-image errors.
Journal mode set, writes serialised
A Dockerfile built on alpine or distroless musl has no glibc, and prebuilt binaries targeted at glibc refuse to load at startup.
Base image matched, binary loading
A pipeline that assumed Node reporters, coverage format or specific CLI flags does not understand what bun test emits.
CI integration adjusted, coverage flowing
What we do
Call us for one install that will not finish, or let us set Bun up across the organisation.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
For many workloads, yes. API servers, scripts, CI pipelines and serverless functions run well on recent releases. Complex Node applications leaning on worker_threads, native addons or specific APM agents still need a careful compatibility check before the switch. We help you decide which bucket your service is in.
Most of the time it is either a Node API Bun has not implemented yet, a native addon without a compatible prebuild, or a library that detects the runtime and takes a different code path. We identify which, pick the right workaround, and leave the rest of the project alone.
Yes, and this is the entry point for a lot of teams. bun install drops into any existing project and produces node_modules the same shape npm would, with a lockfile Bun can read later if you ever want to switch runtimes.
In almost every project we have measured, yes, often by a wide margin. The install step collapses from tens of seconds to under one, and tests tend to run faster because the runner starts fast and parallelises by default. Savings compound on branches that run CI many times a day.
If you want to, yes, but it is rarely the first thing we recommend. Running Express or Fastify on top of Bun usually captures most of the performance win with far less rewrite. Moving to Bun.serve becomes worth it when the service is latency-sensitive enough to care about the final few milliseconds.
A written quote costs nothing. Tell us which service you are moving and what has stopped working, and a price comes back the same day.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: