ArchiveExpo SnackDiscord and ForumsNewsletter


Edit this page

A command-line tool to create a new Expo and React Native project.

create-expo-app is a command-line tool to create and set up a new Expo and React Native project. This tool simplifies the initialization process by providing various templates to get started quickly without the need for manual configuration.

Create a new project

To create a new project, run the following command:

npx create-expo-app@latest
yarn create expo-app
pnpm create expo-app
bun create expo

Running the above command will prompt you to enter the app name of your project. This app name is also used in the app config's name property.

What is your app named? my-app


Uses the following options to customize the command behavior.


Uses the default options to create a new project.


Skips installing npm dependencies or CocoaPods.


Running create-expo-app with a Node Package Manager initializes and sets up a new Expo project using the default template.

You can use the --template option to select one of the following templates or pass it as an argument to the option. For example, --template default.

defaultDefault template. Designed to build multi-screen apps. Includes recommended tools such as Expo CLI, Expo Router library and TypeScript configuration enabled. Suitable for most apps.
blankInstalls minimum required npm dependencies without configuring navigation.
blank-typescriptA Blank template with TypeScript enabled.
tabsInstalls and configures file-based routing with Expo Router and TypeScript enabled.
bare-minimumA Blank template with native directories (android and ios) generated. Runs npx expo prebuild during the setup.


Use this option to initialize a project using an example from expo/examples.

For example, running npx create-expo-app --example with-router will set up a project with Expo Router library.


Prints the version number and exits.


Prints the list of available options and exits.

Node Package Managers support

Creating a new project with create-expo-app also handles setting up additional configuration needed for a specific Node Package Manager.

If you are migrating from one package manager to another, you've to manually carry out the additional configuration in your project. If you are using EAS, you also have to configure your project for any additional required steps manually.

All the additional steps for each package manager are listed below.


Local installation

npm is installed as part of Node.js installation. See Node.js documentation for installation instructions.

EAS installation

Supported by default if the project directory contains package-lock.json.

Yarn 1 (Classic)

Local installation

Yarn 1 (Classic) is usually installed as a global dependency of npm. See Yarn 1 documentation for installation instructions.

EAS installation

Supported by default if the project directory contains yarn.lock.

Yarn 2+ (Modern)

Local installation

See Yarn documentation for installation instructions.

Yarn 2+ handles package management differently than Yarn 1. One of the core changes in Yarn 2+ is the Pug'n'Play (PnP) node linking model that does not work with React Native.

By default, a project created with create-expo-app and Yarn 2+ uses nodeLinker with its value set to node-modules to install dependencies.

nodeLinker: node-modules

EAS installation

Yarn Modern on EAS requires requires adding eas-build-pre-install hook. In your project's package.json, add the following configuration:

  "scripts": {
    "eas-build-pre-install": "corepack enable && yarn set version 4"


Local installation

Requires installing Node.js. See pnpm documentation for installation instructions.

By default, a project created with create-expo-app and pnpm uses node-linker with its value set to hoisted to install dependencies.


EAS installation

Supported by default if the project directory contains pnpm-lock.yaml.


See Bun guide for details on creating a new Expo project with bun, migration from another package manager, and usage with EAS.