Update resolved dependencies #66
Merged
+37
−370
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
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.
By deleting some of the resolutions and running
yarnagain, we can get the latest resolved versions as accepted by the semver notation used by the projects requiring them.This allows us to get more up to date dependencies that fix some known security issues. Those issues were not problematic, since they were all from dev dependencies (required by babel and jest), yet it's nice to keep the project clean from them.
As a nice side effect, this ends up consolidating some of the resolved dependencies, resulting in a smaller
yarn.lock.