Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failed to build dependency graph #30

Closed
aktraore opened this issue Oct 10, 2016 · 1 comment
Closed

failed to build dependency graph #30

aktraore opened this issue Oct 10, 2016 · 1 comment

Comments

@aktraore
Copy link

aktraore commented Oct 10, 2016

I have an error after having installed the module. When building the react-native app, the packager throws a naming collision error saying that there is a duplicate module. This is due to the fact that this module has react-native as a dependency, deleting the react-native folder in the node_modules of this module is a workaround but my question is, why do you need react-native as a dependency of this module, and by that I mean wouldn't be better to have it as a devDevendecy? Using npm 3.10.0, react-native 0.30.0, react-native-cli 1.0.0
2016-10-10_23h46_03

@xotahal
Copy link
Owner

xotahal commented Oct 12, 2016

Hey @AbdoulayeKarimTraore,

you're right, we don't need to have react native as dependency. Sorry for that :/ Fixed in https://github.com/xotahal/react-native-material-ui/releases/tag/v1.3.2

@xotahal xotahal closed this as completed Oct 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants