As an installer Bun 73,307 is close to npm 2,036 , but it does not replace the whole npm CLI. 6 lists the gaps in Bun 1.4.2 that matter in a release pipeline, checked against its own help output.
| Task | Bun 1.4.2 | Use instead |
|---|---|---|
| Log in to the registry | bun login is "reserved for future use" | npm login, or a token in .npmrc |
| Publish with provenance | bun publish has no --provenance flag | npm publish --provenance |
| Manage dist-tags, owners, deprecations | No such commands | npm dist-tag, npm owner, npm deprecate |
| Plug'n'Play resolution | Not supported | Yarn Berry 11,798 |
| Import a Yarn Berry lockfile | UnsupportedYarnLockfileVersion | Re-resolve from package.json |
The everyday set is there: bun add, remove, update, outdated, audit, why, patch, pm pack and a basic bun publish with --tag, --access and --otp. Installing with Bun does not force its runtime on you either: BookNest still starts with node server.js. A common split is Bun for fast installs and npm for account and publishing tasks (MERN Stack Development, Trusted Publishing). Whether Bun is actually faster for BookNest is A Real Install Benchmark's question.