Clean up peer dependencies for new project

[robinheinze]

We have a few unmet or incorrect peer dependencies for newly ignited projects, so we should clean those up where we can.

warning " > [email protected]" has unmet peer dependency "react-art@>= 16.3.2".
warning " > [email protected]" has unmet peer dependency "react-native-web@>= 0.7".
warning "react-navigation > [email protected]" has unmet peer dependency "react-native-screens@^1.0.0 || ^1.0.0-alpha".
warning "react-navigation > [email protected]" has unmet peer dependency "react-native-screens@^1.0.0 || ^1.0.0-alpha".
warning "react-navigation > [email protected]" has unmet peer dependency "react-native-screens@^1.0.0 || ^1.0.0-alpha".
warning " > [email protected]" has unmet peer dependency "reactotron-core-client@^2.5.0".
warning " > @storybook/[email protected]" has unmet peer dependency "babel-runtime@>=6.0.0".
warning "@storybook/react-native > [email protected]" has incorrect peer dependency "babel-core@6".

[JulienMalige]

Is there an easy way to test it after editing the package.json.ejs ?

[JulienMalige]

In fact, I think that yarn considers some dependencies as unmet because of the sub directory trick during the install process (when there are 2 package.json).