Expo CLI - Expo Documentation (2023)

This documentation refers to the Local Expo CLI (SDK 46 and greater). For information on legacy Expo CLI, see

Global Expo CLI.

Highlights

• Start a server for developing your app: npx expo start.
• Generate the native iOS and Android directories for your project: npx expo prebuild.
• Build and run the native apps locally: npx expo run:ios and npx expo run:android.
• Install and update packages that work with the version of react-native in your project: npx expo install package-name.
• npx expo can be used with npx react-native simultaneously.

To view a list of available commands in Expo CLI, run the following in your project:

You can also run yarn expo -h if you prefer to use yarn as the package manager.

The output should look something like below:

Usage $ npx expo Commands start, export, export:web run:ios, run:android, prebuild install, customize, config login, logout, whoami, registerOptions --version, -v Version number --help, -h Usage info

You can run any command with the --help or -h flag to learn more about it:

Develop

Start a development server to work on your project by running:

You can also run npx expo as an alias to npx expo start.

This command starts a server on http://localhost:19000 which a client can use to interact with the bundler. The default bundler is Metro.

Server URL

By default, the project is served over a LAN connection. You can change this behavior to localhost-only by using the flag npx expo start --localhost.

Other available options are:

• --port: Port to start the dev server on (does not apply to webpack or tunnel URLs). Default: 19000.
• --https: Start the dev server using a secure origin. This is currently only supported on web.

You can force the URL to be any value with the EXPO_PACKAGER_PROXY_URL environment variable. For example:

Will open apps to: exp://expo.dev:80 (the :80 is a temporary workaround for Android websockets).

Tunneling

Restrictive network conditions (common for public Wi-Fi), firewalls (common for Windows users), or Emulator misconfiguration can make it difficult to connect a remote device to your dev server over lan/localhost.

Sometimes it's easier to connect to a dev server over a proxy URL that's accessible from any device with internet access, this is referred to as tunneling. npx expo start provides built-in support for tunneling via ngrok.

To enable tunneling, first install @expo/ngrok:

Then run the following to start your dev server from a tunnel URL:

This will serve your app from a public URL like: http://xxxxxxx.bacon.19000.exp.direct:80.

Drawbacks

• Tunneling is slower than local connections because requests must be forwarded to a public URL.
• Tunnel URLs are public and can be accessed by any device with a network connection. Expo CLI mitigates the risk of exposure by adding entropy to the beginning of the URL. Entropy can be reset by clearing the .expo directory in your project.
• Tunnels require a network connection on both devices, meaning this feature cannot be used with the --offline flag.

Offline

You can develop without a network connection by using the --offline flag:

Offline will prevent the CLI from making network requests. If you don't use the flag and your computer has no internet connection, then offline support will automatically be enabled, it will just take a bit longer to verify the reachability.

Expo CLI makes network requests to sign manifests with your user credentials to ensure sensitive information is sandboxed in reusable runtimes like Expo Go.

Building

A React Native app consists of two parts: a native runtime (compiling), and static files like JavaScript bundles and assets (exporting). Expo CLI provides commands for performing both tasks.

Compiling

You can compile your app locally with the run commands:

Highlights

• Build directly on connected devices with no global side effects using the --device flag. Supports locked devices, letting you retry instantly instead of needing to rebuild.
• Automatically codesign iOS apps for development from the CLI without having to open Xcode.
• Smart log parsing show you warnings and errors from your project source code, unlike Xcode which surfaces hundreds of benign warnings from your node modules.
• Fatal errors causing your app to crash will be surfaced to the terminal preventing the need to reproduce in Xcode.

expo run:ios can only be run on a Mac, and Xcode must be installed. You can build the app in the cloud from any computer using eas build -p ios. Similarly, expo run:android requires Android Studio and Java to be installed and configured on your computer.

Building locally is useful for developing native modules and debugging complex native issues. Building remotely with eas build is a much more resilient option due to the preconfigured cloud environment.

If your project does not have the corresponding native directories, the npx expo prebuild command will run once to generate the respective directory before building.

For example, if your project does not have a root ios/ directory, then npx expo run:ios will first run npx expo prebuild -p ios before compiling your app. Learn more about this process in the Expo Prebuild doc.

Cross-Platform Arguments

• --no-build-cache: Clear the native cache before building. On iOS this is the derived data folder. Cache clearing is useful for profiling your build times.
• --no-install: Skip installing dependencies. On iOS this will also skip running npx pod-install if the dependencies field in the project's package.json have changed.
• --no-bundler: Skip starting the dev server. Enabled automatically if the dev server is already serving the app from a different process.
• -d, --device [device]: Device name or ID to build the app on. You can pass --device without arguments to select a device from a list of available options. This supports connected devices as well as virtual devices.
• -p, --port <port>: Port to start the development server. Default: 8081. This is only relevant for development builds. Production builds will export the project and embed the files in the native binary before installing on a device.

Compiling iOS

An iOS app can have multiple schemes for representing different sub-apps like App Clips, watchOS apps, Safari Extensions, and so on. By default, expo run:ios will choose the scheme for your iOS app. You can pick a custom scheme with the --scheme <my-scheme> argument. If you pass in the --scheme argument alone, then Expo CLI will prompt you to choose a scheme from the list of available options in your Xcode project.

The scheme you select will filter out which --device options show up in the selection prompt, for example, selecting an Apple TV scheme will only show available Apple TV devices.

You can compile an iOS app for production by running:

This build is not automatically code signed for submission to the Apple App Store. npx expo run:ios should mostly be used to test bugs that only show up in production builds. Native code signing requires several network requests and is prone to many different types of errors from the Apple servers. To generate a production build that is code signed for the App Store, we recommend using EAS Build.

When you compile your app onto a Simulator, the Simulator's native error logs will be piped to the Expo CLI process in the terminal. This is useful for quickly seeing bugs that may cause a fatal error. For example, missing permission messages. Error piping is not available for physical iOS devices.

You can debug using lldb and all of the native Apple debugging tools by opening the project in Xcode and rebuilding from Xcode:

Building from Xcode is useful because you can set native breakpoints and profile any part of the application. Be sure to track changes in source control (git) in case you need to regenerate the native app with npx expo prebuild -p ios --clean.

iOS development signing

If you want to see how your app will run on your device, all you have to do is connect it, run npx expo run:ios —-device, select your connected device.

Expo CLI will automatically sign the device for development, install the app, and launch into it.

If you don't have any developer profiles setup on your computer then you'll need to set them up manually outside of Expo CLI by following this guide: Setup Xcode signing.

Compiling Android

Android apps can have multiple different variants which are defined in the project's build.gradle file. Variants can be selected with the --variant flag:

You can compile the Android app for production by running:

This build is not automatically code signed for submission to the Google Play Store. This command should be used to test bugs that may only show up in production builds. To generate a production build that is code signed for the Play Store, we recommend using EAS Build.

You can debug the native Android project using native debugging tools by opening the android/ folder in Android Studio:

Exporting

You can export the JavaScript and assets for your app using Metro bundler by running:

This is done automatically when using eas update or when compiling the native runtime. The export command works similar to most web frameworks:

• A bundler transpiles and bundles your application code for production environments, stripping all code guarded by the __DEV__ boolean.
• All static files are copied into a static dist/ folder which can be served from a static host.
• Contents of the public/ folder are copied into the dist/ folder as-is.

The following options are provided:

• --platform <platform>: Choose the platform to compile for: 'ios', 'android', 'all'. Default: all. 'web' is also available if configured in the Expo config. For more information, see Customizing Metro.
• --dev: Bundle for development environments without minifying code or stripping the __DEV__ boolean.
• --output-dir <dir>: The directory to export the static files to. Default: dist
• --max-workers <number>: Maximum number of tasks to allow the bundler to spawn. Setting this to 0 will run all transpilation on the same process, meaning you can easily debug Babel transpilation.
• -c, --clear: Clear the bundler cache before exporting.

Exporting with webpack

webpack is only supported for the Web platform.

You can export the JavaScript and assets for your web app using webpack by running the following:

• --dev: Bundle in 'development' mode without minifying code or stripping the __DEV__ boolean.
• -c, --clear: Clear the bundler cache before exporting.

This command will be disabled if your project is configured to use metro for bundling web projects in the app.json via the expo.web.bundler: 'metro' field.

Prebuild

Native source code must be generated before a native app can compile. Expo CLI provides a unique and powerful system called prebuild, that generates the native code for your project. To learn more, read the Expo Prebuild docs.

Config

Evaluate the Expo config (app.json, or app.config.js) by running:

• --full: Include all project config data.
• --json: Output in JSON format, useful for converting an app.config.js to an app.config.json.
• -t, --type: Type of config to show.

Config Type

There are three different config types that are generated from the Expo config:

• public: The manifest file to use with OTA updates. Think of this like an index.html file's <head /> element but for native apps.
• prebuild: The config that is used for Expo Prebuild including async modifiers. This is the only time the config is not serializable.
• introspect: A subset of the prebuild config that only shows in-memory modifications like Info.plist or AndroidManifest.xml changes. Learn more about introspection.

Install

Unlike the web, React Native is not backwards compatible. This means that npm packages often need to be the exact right version for the currently installed copy of react-native in your project. Expo CLI provides a best-effort tool for doing this using a list of popular packages and the known working version combinations. Simply use the install command as a drop-in replacement for npm install:

Running a single instance of this command, you can also install multiple packages:

You can directly pass arguments to the underlying package manager by using the -- operator:

Version validation

You can perform validation and correction with the --check and --fix flags:

• --check: Check which installed packages need to be updated.
• --fix: Automatically update any invalid package versions.

Example:

npx expo install --check prompts you about packages that are installed incorrectly. It also prompts about installing the these packages to their compatible versions locally. It exits with non-zero in Continuous Integration (CI). This means you can use this to do continuous immutable validation. In contrast, npx expo install --fix will always fix packages if needed, regardless of the environment.

You can validate specific packages by passing them:

The command npx expo install expo-camera and npx expo install expo-camera --fix serve the same purpose, the --fix command is useful for upgrading all packages in your project like:

Install package managers

npx expo install has support for yarn, npm, and pnpm.

You can force the package manager using a named argument:

• --npm: Use npm to install dependencies. Default when package-lock.json exists
• --yarn: Use Yarn to install dependencies. Default when yarn.lock exists
• --pnpm: Use pnpm to install dependencies. Default when pnpm-lock.yaml exists

Authentication

Expo CLI provides authentication methods to use with the npx expo start command. Authentication is used to "code sign" manifests for secure OTA usage. Think of this like HTTPS on the web.

1. Register an account with npx expo register.
2. Login to your account with npx expo login.
3. Check which account is currently authenticated with npx expo whoami.
4. Logout with npx expo logout.

These credentials are shared across Expo CLI and EAS CLI.

Customizing

Sometimes you may want to customize a project file that would otherwise be generated in memory by Expo CLI. When utilizing tools other than Expo CLI, you'll need to have the default config files present, otherwise your app may not work as expected. You can generate files by running:

From here, you can choose to generate basic project files like:

• babel.config.js -- The Babel configuration. This is required to be present if you plan to use tooling other than Expo CLI to bundle your project.
• webpack.config.js -- The default webpack config for web development.
• metro.config.js -- The default Metro config for universal development. This is required for usage with npx react-native.

Environment Variables

• HTTP_PROXY (string) HTTP/HTTPS proxy URL to connect for all network requests. Configures https-proxy-agent.
• EXPO_NO_WEB_SETUP (boolean) prevents the CLI from forcing web dependencies (react-dom, react-native-web, @expo/webpack-config) to be installed before using web functionality. This is useful for cases where you wish to perform non-standard web development.
• EXPO_NO_TYPESCRIPT_SETUP (boolean) prevents the CLI from forcing TypeScript to be configured on npx expo start. For more information, see TypeScript guide.
• DEBUG=expo:* (string) enables debug logs for the CLI, you can configure this using the debug convention.
• EXPO_DEBUG (boolean) an alias for DEBUG=expo:*.
• EXPO_PROFILE (boolean) enable profiling stats for the CLI, this does not profile your application.
• EXPO_NO_CACHE (boolean) disable all global caching. By default, Expo config JSON schemas, Expo Go binaries for simulators and emulators, and project templates are cached in the global .expo folder on your machine.
• CI (boolean) when enabled, the CLI will disable interactive functionality, skip optional prompts, and fail on non-optional prompts. Example: CI=1 npx expo install --check will fail if any installed packages are outdated.
• EXPO_NO_TELEMETRY (boolean) disables anonymous usage collection. Learn more.
• EXPO_NO_GIT_STATUS (boolean) skips warning about git status during potentially dangerous actions like npx expo prebuild --clean.
• EXPO_NO_REDIRECT_PAGE (boolean) disables the redirect page for selecting an app, that shows when a user has expo-dev-client installed, and starts the project with npx expo start instead of npx expo start --dev-client.
• EXPO_PUBLIC_FOLDER (string) public folder path to use with Metro for web. Default: public. Learn more.
• EDITOR (string) name of the editor to open when pressing o in the Terminal UI. This value is used across many command line tools.
• EXPO_EDITOR (string) an Expo-specific version of the EDITOR variable which takes higher priority when defined.
• EXPO_IMAGE_UTILS_NO_SHARP (boolean) disable the usage of global Sharp CLI installation in favor of the slower Jimp package for image manipulation. This is used in places like npx expo prebuild for generating app icons.
• EXPO_TUNNEL_SUBDOMAIN (boolean) Experimental Disable using exp.direct as the hostname for --tunnel connections. This enables https:// forwarding which can be used to test universal links on iOS. This may cause unexpected issues with expo-linking and Expo Go. Select the exact subdomain to use by passing a string value that is not one of: true, false, 1, 0.
• EXPO_METRO_NO_MAIN_FIELD_OVERRIDE (boolean) force Expo CLI to use the resolver.resolverMainFields from the project's metro.config.js for all platforms. By default, Expo CLI will use ['browser', 'module', 'main'], which is the default for webpack, for the web and the user-defined main fields for other platforms.

Telemetry

Expo dev tools collect anonymous data about general usage. This helps us know when a feature is not working as expected. Telemetry is completely optional, you can opt out by using the EXPO_NO_TELEMETRY=1 environment variable.