Conversation
pavgra
approved these changes
Nov 21, 2018
Contributor
|
Hopefully, this is temporary change |
Collaborator
|
I was noticing this too, but thought it was just user error... when I did an npm install it was regenearting the entire .lock file even tho nothing looked changed. I think it might be some line-ending diff between platforms or something. |
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
3 participants
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.
current
package-lock.jsonis generated on windows machine and there are some issues with building on linux one:npm WARN tarball tarball data for file-saver@1.3.8 (sha512-spKHSBQIxxS81N/O21WmuXA2F6wppUCsutpzenOeZzOCCJ5gEfcbqJP983IrpLXzYmXnMUa6J03SubcNPdKrlg==) seems to be corrupted. Trying one more time. npm ERR! code EINTEGRITY