You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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 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.
expo install
does not work for us in a monorepowhich leaves us with no way to find out what version of@react-navigation
packages we need except toexpo init
a new project, thenyarn
thenexpo 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.
The text was updated successfully, but these errors were encountered: