fix corrupted lockfile due to the NPM bug #4828.#189
Open
mreitschuster wants to merge 1 commit intosmartcontractkit:mainfrom
Open
fix corrupted lockfile due to the NPM bug #4828.#189mreitschuster wants to merge 1 commit intosmartcontractkit:mainfrom
mreitschuster wants to merge 1 commit intosmartcontractkit:mainfrom
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
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.
Hi all!
I tried using the newest version to learn how to use VRF 2.5. So i checked out and installed a fresh version with:
results in
After some research it seems to me the package-lock.json should be generated by the npm install command, and not necessarily be part of the git source. Removing the package-lock.json and adding it to the .gitignore fixes the issue.