Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Added Expo 52 Support #1250

Closed
wants to merge 1 commit into from
Closed

Added Expo 52 Support #1250

wants to merge 1 commit into from

Conversation

akhockey21
Copy link

Updated dependencies to work with Expo 52

@akhockey21
Added Expo 52 Support
01d762f 
Add Expo 52 Support
@akhockey21 akhockey21 mentioned this pull request Nov 15, 2024
Open
2 tasks
@g-otn
Copy link

g-otn commented Nov 26, 2024 •
edited
Loading

Shouldn't expo and @expo/config-plugins be peerDependencies anyways? The problem (two different expo versions installed) wouldn't happen then.

@GabrieleMazzola
Copy link

@intent-kacper-cyranowski any hope this will be merged soon?

@GabrieleMazzola
Copy link

In the meantime, I temporarily solved this issue with

  "pnpm": {
    "overrides": {
      "@expo/config-plugins": "9.0.10",
      "expo": "52.0.11"
    }
  }

in my package.json

@aliberski
Copy link
Collaborator

It should be fixed by this PR. We'll release it in the next version

@aliberski aliberski closed this Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@akhockey21 @g-otn @GabrieleMazzola @aliberski