This repository has been archived by the owner on Jan 18, 2024. It is now read-only.
Removed @expo/config dependency #4690
Closed
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
Removed @expo/config dependency that is causing nested dependency version conflicts
|
Be nice to see this pulled in soon so "the Doc" stops being mad at me when I build. |
EvanBacon
reviewed
Aug 15, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Why
Removed @expo/config dependency that is causing nested dependency version conflicts, and instead have it pulled it via the expo devDependency.
Fixes #4688
Same PR as #4512 (Which fixed #4511) - This issue has regressed from commit 3052b9d from #3763.
How
Updated package.json
Test Plan
Tested