Repository navigation
Add bun.lock for faster local installs; drop stale package-lock.json - #160
Merged
Merged
Conversation
…k.json bun install takes about 2 s warm against 5 to 9 s for npm ci. CI and publishing still use npm ci and npm-shrinkwrap.json. package-lock.json disagreed with npm-shrinkwrap.json on 57 versions and npm never reads it while the shrinkwrap exists. Bun migrated from it and picked the wrong versions, so it is removed and bun.lock was generated from the shrinkwrap. Every production package now matches the shrinkwrap. A bun-lockfile workflow fails a PR that changes package.json without updating bun.lock.
cultron
force-pushed
the
chore/bun-install
branch
from
October 27, 2026 20:50
9ccfc42 to
9f6ab9c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
bun installtakes about 5 s cold and under 0.2 s warm, against 5 to 9 s fornpm ci. CI and publishing are unchanged: they still usenpm ciandnpm-shrinkwrap.json.What
bun.lock, generated fromnpm-shrinkwrap.json(Bun 1.4.4).package-lock.json. It disagreed with the shrinkwrap on 57 versions, and npm never reads it while the shrinkwrap exists. Bun migrated from it and picked the wrong versions.bun-lockfileworkflow:bun install --frozen-lockfileon PRs that touchpackage.json,npm-shrinkwrap.jsonorbun.lock, so a dependency change without abun.lockupdate fails.CLAUDE.md: install withbun installornpm ci; afternpm install <pkg>, runbun installand commit both lockfiles.scripts/secret-scan.shskipsbun.locklike other lockfiles.Tested
npm-shrinkwrap.json. The only differences are duplicate nested copies of dev tooling that npm keeps and Bun dedupes.bun run buildandnpm ciboth work; secret scan clean.Known gap
npm updatechanges only the shrinkwrap, sobun.lockcan fall behind without this check catching it.