expo-cli VS cli

$ expo start --dev-client WARNING: expo-cli has not yet been tested against Node.js v18.10.0. If you encounter any issues, please report them to https://github.com/expo/expo-cli/issues

Can you open an issue here with a minimal repro: https://github.com/expo/expo-cli/issues

React Native Modal Datetime Picker is a cross-platform calendar picker for React Native. The library includes a calendar picker component and a time picker component. The calendar picker for this library is presented inside a modal, which looks and feels like native modals for iOS and Android. React Native Modal Datetime is easy to install and supports projects created with Expo CLI and bare React Native projects.

that's certainly odd! any chance you could try cloning the expo-cli repository and debugging this issue locally? https://github.com/expo/expo-cli/

And thanks to @expo/next-adapter, you can even use Next.js to control your Expo for Web app. For details, check "Using Next.js with Expo for Web".

However, the Expo docs on this are outdated. I recommend commenting on this thread if you need help: https://github.com/expo/expo-cli/issues/3579

expo-cli (>= 4.x.x)

Locally, you can run the bundle command, then copy the output files into the binary folder, example: https://github.com/expo/expo-cli/pull/3667/files

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.

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