Impact Score: 5/10
Bun v0.0.56
Source available โ automated, not human-reviewed
Component: bun ยท Channel: stable. Automated analysis, not a compatibility certification. How this works.
Analysis updated: 2026-11-01.
โก Executive Summary (TL;DR)
Bun bun-v0.0.56. Source highlight: Today is an exciting day. Introducing `bun install` โ an incredibly fast npm client.
Who Does This Impact? (Role-Based Analysis)
๐ป Software Engineers & Devs
Check the source notes against the package and APIs you use before upgrading.
๐ Product & Engineering Leads
Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.
โ๏ธ DevOps & Security
Verify the target version, runtime requirements and rollback procedure in the official documentation.
๐ง Bug Fixes & Patches (1)
- `node-gyp` isn't supported yet either, but that will be fixed.
๐ View Raw Release Notes (Original Developer Log)
To upgrade:
```bash
bun upgrade
```
## bun install
Today is an exciting day. Introducing `bun install` โ an incredibly fast npm client.
Before I get into perf numbers, consider this especially early.
- workspaces not implemented yet
- `link:` not implemented yet
- `github:` not implemented yet
- `git:` not implemented yet
- Config file where you can set registry and auth tokens is not implemented yet. That means private packages won't really work yet (though it does read `$npm_config_registry`)
- The lockfile format may change a little in the coming weeks (which would invalidate existing lockfiles)
- postinstall will not be supported (probably won't be [opt-in](https://github.com/npm/rfcs/pull/488) either). `esbuild` and `turbo` get special treatment I'm calling "native bin linking". I plan to write a more generalizable proposal for this that other npm clients can adopt to make shipping binary executables on npm faster & simpler
- `node-gyp` isn't supported yet either, but that will be fixed.
### Linux
**100x faster npm install** for incremental installs. In this case, only react is missing (the cleanup resets node_modules), each package manager has an up-to-date lockfile, and packages have previously downloaded before (disk cache)
<img src="https://user-images.githubusercontent.com/709451/146924903-175dcfbd-c3a5-4a89-860b-c73178b35268.png" />
20x faster than npm install when node_modules is empty. In this case, each package manager has an up-to-date lockfile and packages have also been downloaded before.

When there are no changes, `bun install` is 100x faster than npm install

### macOS
Note: currently macOS installs are single-threaded & parallelism may help when there are > 100 packages, so these numbers may improve later
80x faster npm install for incremental installs.

4x faster npm install when there is no node_modules folder

When there are no changes, 80x faster than npm install

### Autocomplete
Thanks to @evanwashere, `bun add` has autocomplete for the top 10,000 npm packages. It also searches your shell's history to complete from.

Fish completions:

#### Why is it faster?
I will do a longer write up on why it's faster. Zig is part of that, but a lot of work went into data layout, the lockfile format, the https client, the manifest cache format, and a lot of other stuff.