Michał Pierzchała

Please make sure you have all JS deps installed (run `yarn --force` or remove node_modules and try again). Also, what happens when you run `node -e "console.log(require('react-native/cli').bin);"`? Maybe there's some...

It shouldn't be necessary. The `node -e "console.log(require('react-native/cli').bin);"` script is called from `src/node_modules/@react-native-community/cli-platform-android/` directory – can you run it from there? The `require` call searches for the `react-native` module up...

This works as expected. There's no "Cannot find module 'react-native/cli'". I think you'll need to investigate what's wrong on your end. Maybe a different version of Node kicks in, with...

This may happen when you have older react-native project, something below 0.61

Also, this shouldn't happen, unless you have `@react-native-community/cli` in your dependencies. You generally shouldn't and if you have it, please remove.

No, it's expected to be there since RN 0.60 for autolinking feature, so you don't need to manually link anymore. See https://github.com/react-native-community/cli/blob/master/docs/autolinking.md

Would you like to tackle this issue? :)

I was able to successfully run on a different port when running: ``` react-native start --port XX react-native run-android --port XX ``` Can you check yourself?

Now I tried to run `react-native run-android --port XX ` only and it seems that Metro is opened on wrong port indeed. @Taym95 because you've already worked on this, can...

Thank you @Taym95