Clean npm install package-lock.json generate #2011
Merged
Conversation
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
Anemy
force-pushed
the
compare-clean-package-lock
branch
from
d1d23de to
02becd5
Compare
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.
Our
package-lock.jsonhas some extra packages that were introduced db7554a#diff-32607347f8126e6534ebc7ebaec4853dThis PR clean installs and generates package-lock.json.
Hopefully this decreases the size of the generated artifacts: https://github.com/mongodb-js/compass/releases/tag/untagged-6941d81a6c33b14996c1 They doubled ater the package-lock.json additions.