Upgrade kind-of dependency to fix security vulnerability
#158
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
|
Instead of installing https://classic.yarnpkg.com/en/docs/selective-version-resolutions/ |
|
Oh, right! I didn't expand the package.json and I thought those were |
CosmaTrix
approved these changes
Jul 7, 2020
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.
This fixes GHSA-6c8f-qphg-qjgp.
Unfortunately, not all dependencies have released new versions that depend on the latest version of the
kind-ofdependency. Therefore, I suggest fixing this using selective dependency resolutions.We should plan a moment to revisit all dependencies and upgrade the ones that released a patch. This will most likely allow us to clean up the other selective dependency resolutions as well.