Update migration guide from a RN #33
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| - `src/` folder | ||
| ``` | ||
| "plugins": { | ||
| "react-native": "0.73.4" |
There was a problem hiding this comment.
I think about plugins it should be stated, that renative does not use autolinking, which is used by react native, therefore not only the packages need to be moved to renative.json like you show, but should be moved as such:
"react-native": {
"version": "0.73.4",
"source": "rnv"
}
And if for some of their dependencies mapping does not exist, they will need to implement it
|
|
||
| - `app`: This folder contains the main files for your application. | ||
| - `entry`: This folder allows you to configure the launch settings of your app. It is intended for advanced configuration and customization. | ||
| - `pages`: This folder enables you to create individual pages for your application. |
There was a problem hiding this comment.
This should be stated, that is reserved for Next.js, if they don't do web, they don't need it, they can also specify a different folder in appConfigs/renative.json, but this is not just for individual pages for all platforms
|
|
||
| replace `src/` folder content with source content of your app (JS files) | ||
| :::warning Remember to Update Project Configuration Files | ||
| When transferring your project, it's essential not to overlook updating your configuration files. This includes: |
There was a problem hiding this comment.
Maybe should mention that it would be with imports from renative withRnvBabel and such
Description
Related issues