Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(bun): incorrect bun frozen-lockfile command #214

Merged
merged 1 commit into from
Jul 13, 2024

Conversation

mrsekut
Copy link
Contributor

@mrsekut mrsekut commented Jul 12, 2024

Description

Fixed incorrect commands related to the bun frozen-lockfile option.

The original implementation incorrectly used bun install --no-save for the frozen-lockfile option. The correct command should be bun install --frozen-lockfile, as per the bun documentation.

Linked Issues

Additional context

The bun documentation under the bun install section here states:

For reproducible installs, use --frozen-lockfile. This will install the exact versions of each package specified in the lockfile. If your package.json disagrees with bun.lockb, Bun will exit with an error. The lockfile will not be updated.

$ bun install --frozen-lockfile

Additionally, the lockfile section here mentions:

Can I opt out?
To install without creating a lockfile:

bun install --no-save

The previous implementation incorrectly used --no-save in the frozen-lockfile

@antfu antfu changed the title Fix incorrect bun frozen-lockfile command fix(bun): incorrect bun frozen-lockfile command Jul 13, 2024
@antfu antfu merged commit e0816f8 into antfu-collective:main Jul 13, 2024
@mrsekut mrsekut deleted the fix-bun-frozen-option branch July 13, 2024 11:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants