fix: shrinkwrap setting incorrect lockfileVersion#3978
Merged
lukekarrys merged 1 commit intorelease-nextfrom Nov 3, 2021
Merged
fix: shrinkwrap setting incorrect lockfileVersion#3978lukekarrys merged 1 commit intorelease-nextfrom
lukekarrys merged 1 commit intorelease-nextfrom
Conversation
Contributor
Author
|
@wraithgar I realize this conflicts with #3959, so I'm happy to hold off and fix my conflicts after that is merged. |
Contributor
Author
|
Converting to a draft until #3959 is merged. |
lukekarrys
force-pushed
the
lk/3962-shrinkwrap
branch
from
3f8ca9d to
e9e548c
Compare
wraithgar
reviewed
Nov 3, 2021
wraithgar
approved these changes
Nov 3, 2021
Fix: #3962 When created from a hidden lockfile, shrinkwrap was always setting the lockfileVersion to 3. The shrinkwrap command also needed to be updated to log the correct message based on the lockfileVersion config instead of the static lockfileVersion. With these fixes, it was possible to log a better message whenever we are changing the lockfileVersion, either from a config or any existing lockfile. Lastly, the tests for shrinkwrap were completely refactored to use the real npm and test all conceivable scenarios, as well as removing usage of `util.promisify` in favor of `fs.promises` now that we've dropped support for Node 10. PR-URL: #3978 Credit: @lukekarrys Close: #3978 Reviewed-by: @wraithgar
lukekarrys
force-pushed
the
lk/3962-shrinkwrap
branch
from
2e80379 to
e5bfdac
Compare
Merged
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fix: #3962
When created from a hidden lockfile, shrinkwrap was always setting the
lockfileVersion to 3. The shrinkwrap command also needed to be updated
to log the correct message based on the lockfileVersion config instead
of the static lockfileVersion.
With these fixes, it was possible to log a better message whenever we
are changing the lockfileVersion, either from a config or any existing
lockfile.
Lastly, the tests for shrinkwrap were completely refactored to use the
real npm and test all conceivable scenarios, as well as removing usage
of
util.promisifyin favor offs.promisesnow that we've droppedsupport for Node 10.