Provide guidance on package-lock.json and yarn.lock #81
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
allgandalf
approved these changes
Feb 19, 2025
There was a problem hiding this comment.
LGTM!,
-
I also have in mind that we will never let anyone use
--forceflag while installing dependencies -
I also look forward to remove
yarncompletely , for consistency, lets usenpm@eshantri any specific reasons why we have both yarn and npm ?
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.
I am not sure what the expectation is, but it doesn't seem like small contributions should require changes to package-lock.json and yarn.lock files by default.
I added instructions to the contributing section, and moved contributing up in the README before the section on 'how to add stuff'.