Expo CLI

The Expo CLI is a command-line tool that is the primary interface between a developer and other Expo tools.

The expo package provides a small and powerful CLI tool npx expo which is designed to keep you moving fast during app development.

Highlights

• Start a server for developing your app: npx expo start.
• Generate the native Android and iOS 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 <command>

Commands
  start, export
  run:ios, run:android, prebuild
  install, customize, config
  login, logout, whoami, register

Options
  --version, -v   Version number
  --help, -h      Usage info

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

Installation

Expo CLI is included in the expo package. You can install it with npm or yarn:

Projects that are not using Expo Prebuild (also referred to as Bare projects) will need to perform additional setup to ensure all custom Expo bundling features work: Metro: Bare workflow setup.

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:8081 that a client can use to interact with the bundler. The default bundler is Metro.

The UI that shows up in the process is referred to as the Terminal UI. It contains a QR code (for the dev server URL) and a list of keyboard shortcuts you can press:

Launch target

The npx expo start command automatically launches the app in a development build if expo-dev-client is installed in the project. Otherwise, it launches the app in Expo Go.

Alternatively, you can force the launch target by passing the following flags to the command:

• --dev-client: Always launch the app in a development build.
• --go: Always launch the app in Expo Go.

You can also switch the launch target during runtime by pressing S in the Terminal UI. The run commands also use --dev-client after compiling the development build, by default.

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). Use --port 0 to automatically use the first available port. Default: 8081.
• --https: (Deprecated in favor of --tunnel) 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: https://xxxxxxx.bacon.19000.exp.direct:80.

Use the EXPO_TUNNEL_SUBDOMAIN environment variable to experimentally set the subdomain for the tunnel URL. This is useful for testing 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.

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.

Tunneling requires a third-party hosting service, this means it may sometimes experience intermittent issues like ngrok tunnel took too long to connect or Tunnel connection has been closed. This is often related to intermittent connection problems with the Ngrok servers.... Be sure to check for Ngrok outages before reporting an issue. Some Windows users have also reported needing to modify their antivirus settings to allow Ngrok to work correctly.

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.

.expo directory

When you start the development server in a project for the first time, a .expo directory is created at the root of that project. It contains two files:

• devices.json: Contains information about devices that have opened this project recently.
• settings.json: Contains information about server configuration that is used to serve the project's manifest.

Both of these files have information that is specific to your local computer. This is the reason why .expo directory is included in the .gitignore file, by default, when a new project is created. It is not meant to be shared with other developers.

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 shows 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 in the terminal preventing the need to reproduce in Xcode.

npx 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, npx 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 pre-configured 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 an ios directory in the root of your project, then npx expo run:ios will first run npx expo prebuild -p ios before compiling your app. For more information on this process, see Expo Prebuild.

Cross-platform arguments

• --no-build-cache: Clear the native cache before building. On iOS, this is the derived data directory. 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 has 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 them on a device.
• --binary <path>: File path to the binary to install on the device. When this is provided, the build process will be skipped and the binary will attempt to be installed directly. If the binary was not built for the correct device, for example, it is built for the simulator or installed on the device, then the command will fail.

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:

debug variant

Use the debug variant for a debug build:

debugOptimized variant

debugOptimized is available in SDK 54 and later.

Use the debugOptimized variant for faster development with performance close to release builds while keeping the overall build in a debug-friendly mode:

When using this variant, keep the following in mind:

• Optimizes C++ libraries as in release builds, improving runtime performance
• In EAS Build, use a matching Gradle command like :app:assembleDebugOptimized in eas.json
• Limitation: C++ debugging is disabled and C++ crashes may have less readable stack traces

release variant

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.

Debugging native Android project

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

If you have a customized Android project using different product flavors, you can configure both the flavor and application ID using the --variant and --app-id flags:

For more information, see the Local builds using Android product flavors guide.

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, npx 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, and select your connected device.

Expo CLI will automatically sign the device for development, install the app, and launch 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.

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 directory which can be served from a static host.
• Contents of the public directory are copied into the dist directory 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 app 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.
• --no-minify: Skip minifying JavaScript and CSS assets.
• --no-bytecode: Skip generating Hermes bytecode for native platforms. Only use this for analyzing bundle sizes and never ship UTF-8 bundles to native platforms as this will lead to drastically longer startup times.
• --no-ssg: Skip exporting static HTML files for web routes. This option only generates server code inside the dist directory. Useful for API routes.

Hosting with sub-paths

Experimental functionality.

You can configure the prefix for static assets by setting the experiments.baseUrl field in your app config:

{
  "expo": {
    "experiments": {
      "baseUrl": "/my-root"
    }
  }
}

This will export the website with all resources prefixed with /my-root. For example, an image at assets/image.png will be expected to be hosted at /my-root/assets/image.png. The actual file will be located in the same file system location as the entire directory is expected to be hosted at /my-root on the server.

Expo Router has built-in support for baseUrl. When using the Link and router APIs, the baseUrl will be automatically prepended to the URL.

import { Link } from 'expo-router';

export default function Blog() {
  return <Link href="/blog/123">Go to blog post</Link>;
}

This will export to the following:

<a href="/my-root/blog/123">Go to blog post</a>

If you use <a>, React Navigation, or the Linking API directly, you'll need to manually prepend the baseUrl.

The baseUrl functionality is production-only and must be set before exporting the website. If you change the value, you must re-export the website.

Images and other assets will work automatically if you require or import them. If you directly reference a resource URL then you will need to append the baseUrl manually.

import { Image } from 'expo-image';

export default function Blog() {
  return <Image source={require('@/assets/image.png')} />;
}

This will export to the following:

<img src="/my-root/assets/assets/image.png" />

Manually passing a URL will need to be manually prefixed:

export default function Blog() {
  return <img src="/my-root/assets/image.png" />;
}

Exporting with webpack

Deprecated: In SDK 50 and later, Expo Webpack has been deprecated in favor of universal Metro (npx expo export). Learn more in migrating from Webpack to Expo Router.

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.

Lint

Linting helps enforce best practices and ensure your code is consistent. The npx expo lint command will set up ESLint with Expo-specific settings and run the npx eslint command with options that are optimized for the Expo framework. By running npx expo lint --fix, linting issues can be fixed automatically.

Running npx expo lint targets all files in the src, app, and components directories by default. You can also pass custom files or directories to the lint command as arguments. For example:

All files matching .js, .jsx, .ts, .tsx, .mjs, .cjs extensions will be linted by default. You can customize the extensions by passing the --ext flag. For example, to lint only .ts and .tsx files, you can use the --ext option: npx expo lint --ext .ts,.tsx or npx expo lint --ext .js --tsx .tsx.

If you need additional customization, you can pass extra arguments using the -- operator. For example, to pass the --no-error-on-unmatched-pattern flag to ESLint, you can run:

If you need more customization, you can use npx eslint directly.

Config

Evaluate the app 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 app 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 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:

Configuring dependency validation

There may be circumstances where you want to use a version of a package that is different from the version recommended by npx expo install. In this case, you can exclude specific packages from version checking by using the expo.install.exclude property in your project's package.json.

Install package managers

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

You can force the package manager using a named argument:

• --bun: Use bun to install dependencies. Default when bun.lockb or bun.lock exists.
• --npm: Use npm to install dependencies. Default when package-lock.json exists.
• --pnpm: Use pnpm to install dependencies. Default when pnpm-lock.yaml exists.
• --yarn: Use yarn to install dependencies. Default when yarn.lock 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.
• tsconfig.json -- Create a TypeScript config file and install the required dependencies.

Environment Variables

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.