How to make pnpm update --latest
update package.json even if lockfile is up to date
#7803
Unanswered
WoodyWoodsta
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This may be a carry over in thinking from Yarn (and renovate, although we are still using it), but when I update dependencies using
pnpm update --latest
, even if the lockfile has the resolved version as up to date, I'd like the package.json to also be updated.For example, if I have
"packageA": "^1.0.0"
, and the lockfile has resolved to1.0.1
, is there a way to bump the package.json to"packageA": "^1.0.1"
without me having to root around the lockfile and the package.json manually?The justification for expecting this is that when the lockfile isn't up to date, then this command does actually update the package.json. So I'd intuit that the behaviour be reflected in all situations.
Beta Was this translation helpful? Give feedback.
All reactions