Apply npm install to package-lock.json
#6517
Closed
+20
−0
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
It's not clear what happened in parse-community#6478, but it appears that it dropped the `ws` dependency of the `parse` package when it was updating the local version of the dependency. This means that running `npm install` dirties the working tree, which is surprising! A similar problem seems to have occurred in parse-community#6504, that time related to the `commander` package. I've filed an issue for the surprising behavior from greenkeeper: greenkeeperio/greenkeeper-lockfile#250
|
probably an npm version mismatch |
|
Closing as will be addressed in #6560 |
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.
It's not clear what happened in #6478, but it appears that it dropped
the
wsdependency of theparsepackage when it was updating thelocal version of the dependency. This means that running
npm installdirties the working tree, which is surprising!
A similar problem seems to have occurred in #6504, that time related to
the
commanderpackage.I've filed an issue for the surprising behavior from greenkeeper:
greenkeeperio/greenkeeper-lockfile#250