Replies: 3 comments 3 replies
-
|
This sounds reasonable - would you mind making directly a PR so that it can be discussed "code in hands"? |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
i like the idea of having the version of Node in the project too with an .nvmrc file. is this planned to be added eventually as well? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@barbieri Should we move .ruby-version and Gemfile to ios directory? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The
template/iosusesPodfileand that is based on Ruby and CocoaPods.To aid the process we could provide a
Gemfileand associatedGemfile.lockwith the recommended ruby and CocoaPods version, this way we avoid issues such as using the incorrect versions. Then we change every reference to Executepod installto be Executebundle exec pod installto make sure the correct versions are used.By providing a
.ruby-versionfile, we could help http://rbenv.org/ and https://rvm.io/ uses to use the correct version and avoid pitfalls (such as using the default macOS version, that is a universal binary and may cause issues with ffi on arm64/m1).Along these lines, we could also provide
.nvmrcwith the tested/recommended version and even lockpackage.jsonwithengines: { node: "..." }, this way we minimize problems.I also reported it to react-native-community/react-native-template-typescript#225, but it was said that this change should go in React-Native itself and then they will adapt in future releases.
Beta Was this translation helpful? Give feedback.
All reactions