We’ve got an Expo project that imports a private NPM package called
js-ui-components, which has
react-native as a devDependency. Basically it’s a separate repo in which we put common reusable chunks of UI, and some of them use
react-native components and utils.
Problem is, our main project that’s depending on our private
js-ui-components ALSO requries
react-native as a devDependency. When we use
yarn link to develop this dependency locally, it leads to
Ambiguous resolution errors because “there are several files providing this module” (
I’m also getting these issues when pushing the dependency to a branch on Github and including it that way. The only way it seems to build is if we just depend on the most up-to-date version in NPM, which is really inconvenient for development.
Anyone run into something like this before?