Repository navigation
fix(ci): should not use package-lock config - #4364
Merged
ruyadorno merged 1 commit intoFeb 3, 2022
Merged
Conversation
ruyadorno
added
Release 8.x
Contributor
|
Can we add a test? |
Contributor
Author
I'll add a check alongside the one we have to validate that |
`npm ci` should never be affected by the `package-lock` config. Fixes: npm#4185
ruyadorno
force-pushed
the
npm-ci-ignore-package-lock-config
branch
from
February 3, 2022 15:39
f9f6a63 to
7ddec04
Compare
wraithgar
approved these changes
Feb 3, 2022
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.
npm cishould never be affected by thepackage-lockconfig.References
Fixes: #4185