Therefore, you won’t be able to update React Native until all platforms are ready to support it.Įven though this limitation may not seem like an issue at first, it might get you stuck on older versions of React Native if even a single platform is not compatible with the latest versions. …but, from my personal experience, it has a few drawbacks that get exponentially worse the more your codebase grows.įirst and foremost: you’re forced to use the same version of React Native on every platform you support. This structure can work perfectly fine for most use cases. The most common and straightforward way to support different platforms with a single React Native codebase is to store all the configuration files required to run the app on all platforms in a single project directory.įor example, if you’re planning to support Android, iOS, Windows, and macOS, by following the React Native for Windows + macOS documentation, you’ll end up with a project that looks like this: We’ve been able to run React Native on the web, macOS, and Windows for quite a while now. Running React Native on multiple platforms is not a new thing.
Matteo Mazzarolo Running React Native everywhere: Yarn Workspaces monorepo #react-native, #javascript TL DRįirst part of the “Running React Native everywhere” series: a tutorial about structuring your monorepo to run multiple React Native apps targeting different platforms.
0 kommentar(er)
