Very insightful talk Callum, thanks! Would love to see more content like this and deeper insights into the monorepo architecture in React Native, especially when it comes to supporting multiple platforms
is nohoist still needed to solve the native code not following symlinks issues? I know that since react native 0.73 the metro support is solved, but what about native code support?
We used nx, which allowed to avoid hoisting issues. The only issues so far were related to the location of the entry file or node_modules, these URIs had to be edited.
Are there other instances of not hoisting other modules beside react-native. Full disclosure attempting to run react-native app and a react app with pnpm in a mono repo and running into the same issue where it couldn't identify the package react-native-community-cli
Very insightful talk Callum, thanks! Would love to see more content like this and deeper insights into the monorepo architecture in React Native, especially when it comes to supporting multiple platforms
Finally symlink problem is resolved by default in 0.73 :D
Wonderful video. Thank you for publishing!
Very helpful thanks.
Very informative and sharp edged hoodie! nice job!
is nohoist still needed to solve the native code not following symlinks issues? I know that since react native 0.73 the metro support is solved, but what about native code support?
We used nx, which allowed to avoid hoisting issues. The only issues so far were related to the location of the entry file or node_modules, these URIs had to be edited.
Are there other instances of not hoisting other modules beside react-native. Full disclosure attempting to run react-native app and a react app with pnpm in a mono repo and running into the same issue where it couldn't identify the package react-native-community-cli