You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it seems like the only time frozen-lockfile will be enabled by default is if you use --production, so what would this flag do? Are you possibly passing both at same time and want --no-prefer-frozen-lockfile to override and make it not do frozen?
Today, bun install doesn't assume a frozen lockfile unless you specify it. However, I could see bun going the direction of many other package managers and automatically enabling --frozen-lockfile if CI=true in the environment.
What is the problem this feature would solve?
Many other package managers have a flag to disable
--frozen-lockfile
:pnpm
:--no-prefer-frozen-lockfile
yarn
:--no-immutable
What is the feature you are proposing to solve the problem?
Ensures 100% that you don't enforce frozen lockfile - see aws/aws-cdk#32906
According to this GitHub search, people already seem to think we can do this:
..can we? does the CLI automatically invert all flags with
--no-<regular-flag>
? I couldn't find docs on that.What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: