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.

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

[docs] PLEASE include the proper versions of supported packages per Expo version #8129

Closed
Nantris opened this issue May 3, 2020 · 5 comments
Assignees

Comments

@Nantris
Copy link
Contributor

Nantris commented May 3, 2020

expo install does not work for us in a monorepo which leaves us with no way to find out what version of @react-navigation packages we need except to expo init a new project, then yarn then expo install [whatever packages].

Edit: I'm dumb and this isn't as bad as I had thought - but it would be really nice to be able to find the correct versions listed alongside the releases. I feel like this used to be done with prior SDK blog announcements.

This issue persistently makes trouble for us with a mono-repo and while there's a workaround, the packagification of the ecosystem and the time involved in running yarn/rebuilding via metro bundler is quite substantial. Screw up one package and you're in for another 10 minute run through those two things.

@Nantris Nantris added the docs label May 3, 2020
@Nantris
Copy link
Contributor Author

Nantris commented May 4, 2020

A possibly better alternative would be a command line flag that updates the package.json in that directory without running any actual yarn/npm installations.

@cruzach
Copy link
Contributor

cruzach commented May 11, 2020

thanks, that's a good point and we should add it to the docs

In the meantime- you can find the list of version supported by the sdk by looking at the bundledNativeModules.json file on the sdk-xx branch (where xx is the sdk version)

this is for sdk 37:
https://github.com/expo/expo/blob/sdk-37/packages/expo/bundledNativeModules.json

@cruzach cruzach self-assigned this May 11, 2020
@Nantris
Copy link
Contributor Author

Nantris commented May 16, 2020

That is super helpful! Thank you @cruzach!

@github-actions
Copy link
Contributor

This issue is stale because it has been open for 60 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

@github-actions github-actions bot added the stale label Feb 17, 2022
@github-actions
Copy link
Contributor

This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants