fix: remove yarn.lock and package-lock.json from .gitignore #65
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
## What Removes `yarn.lock` and `package-lock.json` from `.gitignore` ## Why During deployments, this can cause an error if the `yarn.lock` and `package-lock.json` are not committed as part of the repository. An example of that is when deploying to digitalocean which causes an error of no package manager being found.
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.
What
Removes
yarn.lockandpackage-lock.jsonfrom.gitignoreWhy
During deployments, this can cause an error if the
yarn.lockandpackage-lock.jsonare not committed as part of the repository. An example of that is when deploying to digitalocean which causes an error of no package manager being found.