chore: ignore the package-lock.json file when using the pnpm
#63
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
sparrowsl
changed the title
package-lock.json file when using the pnpm package manager
sparrowsl
changed the title
package-lock.json file when using the pnpm package managerpackage-lock.json file when using the pnpm
sparrowsl
force-pushed
the
hide-package-lock
branch
from
b5a89a5
to
a13c6a2
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.
depends on #62 being closed.
running
npm installgenerates thepackage-lock.jsonfile.Since we will use
pnpm-lock.yml(as lockfile) we can ignore thepackage-lock.jsonfile from being committed.