-
-
Notifications
You must be signed in to change notification settings - Fork 936
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
expo@40 support #3321
Comments
SHA-1 for file ... is not computedThe SHA-1 for file ... is not computed issue regarding globbing dotfiles was fixed in WorkaroundNOTE: You need pnpm@6 to allow pinning version of override. package.json "pnpm": {
"overrides": {
"jest-haste-map@24.9.0": "npm:@vjpr/jest-haste-map@24.9.0"
}
} VersioningYou must ensure same version of metro is being used. This can be difficult if using two versions of metro in your codebase...
|
@electroheadfx Does https://github.com/vjpr/pnpm-expo-example work for you? |
thanks @vjpr, yes I did on the package/expo, the compilation is very verbose, how I can uncheck it ? Iam not sure to understand the purpose of package/pnpm-expo-helper. Great from you |
Closing for #3731 |
Just an issue to track expo + pnpm support.
Working example (Apr 2021)
TODO
https://github.com/vjpr/pnpm-expo-exampleVersions
See here for Expo versioning guide: http://docs.expo.io/versions/latest/sdk/index.html#sdk-version
Expo SDK = 40.0.0
React Native = 0.63.3
Installed versions
Github Issues
Previous pnpm+expo notes:
Metro:
Reference
https://dev.to/expo/expo-sdk-40-is-now-available-1in0
Summary
Difficulty arose when trying to support
react-native@0.64
andexpo@40
which only supportsreact-native@0.59
. There were many clashes which can be seen below.I managed to resolve them all, which now means you can have Expo projects in the same repo as latest
react-native
.Will look to publish a working repo eventually.
The text was updated successfully, but these errors were encountered: