Make the FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILE error and hint messages more clear
#6304
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ages more clear The original message was too confusing as per this post last year: https://github.com/orgs/pnpm/discussions/4847
…D_LOCKFILE error message
…ILE error message
|
💖 Thanks for opening this pull request! 💖 |
lvqq
reviewed
Mar 29, 2023
zkochan
approved these changes
Mar 29, 2023
|
Congrats on merging your first pull request! 🎉🎉🎉 |
|
There need to be better errors. I'm not just looking for workspace is out of sync but how. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The current error and hint messages for
FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILEis not very straightforward in explaining what the issue is.This PR attempt to fix this by being a bit more explicit as to what the required upgrade is (lockfile version incompatibility).
The original message was too confusing as per this post last year: https://github.com/orgs/pnpm/discussions/4847