rnx-kit VS cli

Have you seen @rnx-kit/align-deps? Not sure if it’s exactly what you’re looking for, but might be.

Take a look at https://github.com/microsoft/rnx-kit. It’s an upgrade helper tool, helps to ensure that all your packages are compatible (as best it can) with your RN version. Built by MicroSoft and they use it to handle RN upgrades to their software.

From Microsoft: https://github.com/microsoft/rnx-kit

I’ve used this tool to help with upgrades. Might help you? https://github.com/microsoft/rnx-kit

Maintaining a React Native app built in 2017. Biggest pain right now is using the Metro bundler. Since migrating our codebase from a Yarn v1 workspace to a Rush (pnpm-based) monorepo, our packages use symlinks which the Metro bundler doesn't support. I've had to go through solutions such as Microsoft's @rnx-kit/metro-resolver-symlinks but still end up with issues. Will look next in to trying Callstack's repack for building our apps instead of Metro, even though I'm very hesitant in switching build tools.

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