[CHORE] Solve dependabot-raised security issues#1171
Open
Conversation
3069881 to
eb2a425
Compare
This file contains hidden or 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.
What does this PR do?
This PR updates versions os dev Dependencies that have been marked as having security issues by dependabot.
In particular, the fixes are as follows:
Also, on example and exmple-new-architecure I've added
unstable_enablePackageExports: trueandunstable_conditionNameswithreact-nativeso metro supports package exports and it is able to directly import axios without having to also import crypto, which is required on the old-style bundle. Since the example apps don't need it it's better to import just axios in this manner. The benchmark app is not affected by this.Motivation
We should avoid security issues on the SDK, even for dev dependencies.
Review checklist (to be filled by reviewers)