type

BunLockFile

catalog?: Record<string, string>
catalogs?: Record<string, Record<string, string>>
configVersion?: 0 | 1
0 / undefined for projects created before v1.3.2, 1 for projects created after.
Right now this only changes the default install linker strategy:
With 0, the linker is hoisted.
With 1, the linker is isolated for workspaces and hoisted for single-package projects.
lockfileVersion: 0 | 1
overrides?: Record<string, string>

__index[

pkg: string

}

INFO = { prod/dev/optional/peer dependencies, os, cpu, libc (TODO), bin, binDir }

// first index is resolution for each type of package
npm         -> [ "name@version", registry (TODO: remove if default), INFO, integrity]
symlink     -> [ "name@link:path", INFO ]
folder      -> [ "name@file:path", INFO ]
workspace   -> [ "name@workspace:path" ] // workspace is only path
tarball     -> [ "name@tarball", INFO ]
root        -> [ "name@root:", { bin, binDir } ]
git         -> [ "name@git+repo", INFO, .bun-tag string (TODO: remove this) ]
github      -> [ "name@github:user/repo", INFO, .bun-tag string (TODO: remove this) ]

patchedDependencies?: Record<string, string>
trustedDependencies?: string[]
workspaces: {
__index[
workspace: string
]: BunLockFileWorkspacePackage;
}

Types for bun.lock