Ensure latest peerDependencies are checked #8
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.
When checking
peerDependencies
if a package is found to have dependencies query npm for the current versions. If the latest version allowed by the current range is greater than the installed version query NPM for thepeerDependencies
list instead of using the localpackage.json
. This ensures that newer allowed version's requirements are met.There are two edge cases where this isn't correct:
peerDependencies
to a package that previously didn't have any.peerDependencies
so this can't be fixed unfortunately.Fixes #7.