chore: suggest correct lockfile upgrade command #23986
Open
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
The flag
--frozen-lockfileis a yarn flag, not an npm flag.If the goal is to only do a lockfile upgrade, not an install,
npm i --lockfile-version 3 --package-lock-onlyis the flag.But if the intent is to get
npm cioryarn install --frozen-lockfiletype divergence protection, neither of those allow writing to the lockfile so they couldn't perform the version upgrade anyways.Be aware, if there is divergence between the package.json and the lockfile,
npm i --package-lock-onlywill update the lockfile dep tree! But the current command does that as is, in addition to installing all the dependencies.How did you verify your code works?
We noticed the log message when setting up bun CI with a v1 lockfile lodash/lodash#6023 (comment)
To repro