I believe this already exists in Bun as an option:

bun install --frozen-lockfile

From the docs:

To install with reproducible dependencies, use --frozen-lockfile. If your package.json disagrees with bun.lockb, Bun will exit with an error. This is useful for production builds and CI environments.

Could you make bun ci an alias of that, since I wasn't easily able to find that subcommand and it's one that would see really common use?

I believe this already exists in Bun as an option:

bun install --frozen-lockfile

From the docs:

To install with reproducible dependencies, use --frozen-lockfile. If your package.json disagrees with bun.lockb, Bun will exit with an error. This is useful for production builds and CI environments.

im getting error

error: lockfile had changes, but lockfile is frozen

when trying to execute it in my github actions like this - run: bun install --frozen-lockfile && bun run build

I believe this already exists in Bun as an option:

bun install --frozen-lockfile

From the docs:

To install with reproducible dependencies, use --frozen-lockfile. If your package.json disagrees with bun.lockb, Bun will exit with an error. This is useful for production builds and CI environments.

im getting error

error: lockfile had changes, but lockfile is frozen

when trying to execute it in my github actions like this - run: bun install --frozen-lockfile && bun run build

That would happen with npm ci too - both fail with an error if your lockfile doesn't match package.json.

Lots of CI scripts already use npm ci, of course bun has flag, but I'm sure that change npm to bun will be more clear for non JS developers or DevOpsers. Moreover, bun already do it for other npm commands.

make it please, it makes sense

Any time plan for this feature?

yeah... bun install --frozen-lockfile is long af why not just bun ci its so short and memorable

+1
Useful to migrate preinstall hook script.

yeah... bun install --frozen-lockfile is long af why not just bun ci its so short and memorable

Just write a makefile