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

bun install --frozen-lockfile creates bun.lock, even if package-lock.json exists #16646

Open
staabm opened this issue Jan 23, 2025 · 0 comments
Labels
bug Something isn't working bun install Something that relates to the npm-compatible client

Comments

@staabm
Copy link
Contributor

staabm commented Jan 23, 2025

What version of Bun is running?

1.2.0+b0c5a7655

What platform is your computer?

Darwin 24.2.0 arm64 arm

What steps can reproduce the bug?

in bun 1.1.x running bun install --frozen-lockfile did not generate a bun lockfile.
since bun 1.2.x it seems a lockfile is always generated.

What is the expected behavior?

I wonder whether its expected or whether bun install --frozen-lockfile should not generate a new lock file when package-lock.json exists

What do you see instead?

No response

Additional information

No response

@staabm staabm added bug Something isn't working needs triage labels Jan 23, 2025
@RiskyMH RiskyMH added bun install Something that relates to the npm-compatible client and removed needs triage labels Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working bun install Something that relates to the npm-compatible client
Projects
None yet
Development

No branches or pull requests

2 participants