Bump react-scripts to upgreade vuln object-path dependency #207
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
ikornienko
approved these changes
Oct 22, 2020
vjwilson
deleted the
vjw/bump-react-scripts-to-upgrade-vuln-object-path-dependency
branch
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.
Description
Fixes the security warning sent by GitHub, even though it's not an exploitable vuln, since it's only run at build time.
It was a vuln in a sub-package, four levels deep, included because of React helpers scripts.
Facebook went ahead and force-upgraded it, because one of the transitive dependencies had pinned a version of another transitive dependencies, because who knows.
Gory details here:
facebook/create-react-app#9842
Checklist
Testing Performed