cli VS react-native-navigation

It's not typical. Try this

It has been fixed here: https://github.com/react-native-community/cli/pull/1099

I have created a react-native-community/cli template that has RN 0.61.5 project and the required modifications to build Fresco from source. This is an easy and quick way to have a new RN project crafted with custom project name and with the changes needed to compile Fresco from source. It also uses Android NDK Revision 21 and I have tested it on macOS and Windows using yarn 1.21.

In the past Expo was more sandboxed and had less features, so the community would take features like autolinking and put them in a more free form tool called ‘React Native community CLI’ (example https://github.com/react-native-community/cli/issues/248).

Below, we are going to initialise a bare React Native app using React Native CLI and add the necessary libraries. After that, we will configure a navigation state, build two components and push/show/pop between them.

esy uses a plug'n'play install method similar to yarn (and has a caveat about not all npm packages supporting that) but I'm not sure if it has the ability to opt out of it like yarn does with nodeLinker: node-modules in /.yarnrc.yml for packages that only work that way such as the React Native CLI or the Angular CLI (both of which have open issues related to Yarn PnP support as of the time of posting). Is it safe to assume that most normal packages that aren't full-blown frameworks (with a lot going on under the hood) will probably work fine? That's the impression I'm getting from the ones I've tried installing so far.

theres currently a discussion going on about it here: https://github.com/react-native-community/cli/issues/1111

The fastest and easiest way to get started with Vue Native is to bootstrap a mobile app with the Vue Native CLI. This CLI generates a simple, one-page application using either the Expo CLI or React Native CLI under the hood.

I did end up finding the official React Native Guide that points to esemek's repo but it wasn't easy to find because it's in the init.md of the react-native-community/cli repository here https://github.com/react-native-community/cli/blob/master/docs/init.md#creating-custom-template

Looks like this feature is not available (check here and here) yet. Good luck mate

another option is react-native-navigation which I haven't used yet but as the document says:

The behavior was reported in their issues 2 years ago: https://github.com/wix/react-native-navigation/issues/6174

At this point don't have a clear preference over which package to use in my next project (react-navigation or react-native-navigation) - they both have strengths and weaknesses, one is easier to actually work with, one is faster in terms of execution, one has better APIs, docs, community, etc.

class Home extends React.PureComponent { constructor(props: Props) { super(props); Navigation.events().bindComponent(this); } closeMenu = () => { this._drawer.close(); }; openMenu = () => { this._drawer.open(); }; static options(passProps) { return { topBar: { rightButtons: [ { component: { name: 'MenuButton', passProps: { onClick: () => this.openMenu(), }, }, }, ], }, }; } render() { return ( ... ); }} Reference I got my passProps code from: https://github.com/wix/react-native-navigation/issues/3648

Thanks! React Native to build the app. React Native Navigation from Wix to build the navigation so the app feels native.

There are two major navigation libraries in React Native world: react-navigation and react-native-navigation. They are both widely used among the community.

You can have a look at React Native Navigation: https://wix.github.io/react-native-navigation/

To navigate between screens, you will probably end up using the very popular React Navigation library. There is a great, purely native alternative, React Native Navigation (the names get confused easily), from Wix. It is super performant but not that flexible. Therefore, again: If your design asks you for something custom, you have no choice but to go with React Navigation; luckily, it is a great, well-documented option.