1. Write the lockfile
bun install resolves versions and writes bun.lock, a text lockfile that pins the exact dependency tree.
bun installTyporithm · easy
Step 1 of 8 · intro card
Package Manager
Bun writes a text bun.lock lockfile (older Bun used the binary bun.lockb) that pins the exact dependency tree for deterministic installs. Use bun install --frozen-lockfile in CI to fail on any drift, and bun outdated to see what could be updated.
bun install writes a lockfile that records the exact resolved version of every dependency; current Bun uses a human-readable text bun.lock, while older versions wrote the binary bun.lockb.
Committing the lockfile makes installs deterministic — anyone running bun install gets the identical tree, and bun install --frozen-lockfile makes CI fail if the lockfile would otherwise change.
bun outdated reports which dependencies have newer versions available, letting you decide on upgrades without touching the lockfile until you choose to.
bun.lock (text) pins the exact tree; older Bun used binary bun.lockb.
Commit the lockfile so installs are deterministic.
--frozen-lockfile makes CI fail on any lockfile drift.
bun install
bun install --frozen-lockfile
bun outdatedConnect each part of the code to the concept before you type.
bun install resolves versions and writes bun.lock, a text lockfile that pins the exact dependency tree.
bun install--frozen-lockfile fails if the lockfile would change, guaranteeing CI installs exactly what is committed.
bun install --frozen-lockfilebun outdated lists dependencies that have newer versions available, without modifying anything.
bun outdatedRead the concept map and follow the code breakdown.
Type the implementation, repair mistakes and work through every recall exercise.
Use the final check without hints; revisit weak concepts in short practice sessions.