Yes its a bug report
yes
Environment:
OS: macOS Sierra 10.12.6
Node: 7.0.0
Yarn: Not Found
npm: 3.10.8
Watchman: 4.7.0
Xcode: Xcode 9.0 Build version 9A235
Android Studio: 2.3 AI-162.3934792
Packages: (wanted => installed)
react: 16.0.0-alpha.12 => 16.0.0-alpha.12
react-native: ^0.48.4 => 0.48.4
(Write your steps here:)
To return no npm ERR
it returns 2 npm errors:
[email protected] /Users/jmoretti/Git/logitech/ux-smarthome/OperaSetup
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]
npm ERR! peer dep missing: react@>=15.4.0, required by [email protected]
npm ERR! peer dep missing: react@> 15.0.0, required by [email protected]
This is an issue with create-react-native-app, can you re-open this issue over there?
@ide - this should not be closed and is an issue that should be within this repo rather than create-react-native-app ones.
This is because your quick start deployment guideline from https://facebook.github.io/react-native/docs/getting-started.html is exclusively contingent on this tool, and therefore it becomes (in my opinion) your responsibility to make sure it is maintained rather than for your users to.
create-react-native-app is maintained by several of the same people and the root issue is there. The actionable thing that a maintainer of the react-native repo can do is to point you at a more precise repo to open the issue.
@ide that is one method (getting your users to do the work). The other is for your team to point to this issue on their repo instead, which reduces the frustration for your users.
Anyways I have added it here: https://github.com/react-community/create-react-native-app/issues/420
Thanks
@ide - No one resolved this issue yet...
Having the same problem as well... Desperately waiting for a fix!
@sm1th - expo is the one that is throwing this off check this out:
https://github.com/expo/expo/issues/726
Thanks @julesmoretti, turns out it is fine to ignore these errors. I thought this was somehow causing npm start not to work, but if I had read the error that npm start was giving more carefully I could have just installed watchman and continued on with my day 👍
Most helpful comment
Having the same problem as well... Desperately waiting for a fix!