Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

npm install --global expo-cli fails, or the legacy expo-cli will not run on new Node.js

Errornpm install expo-cli --global fails

Short answer

The global expo-cli is the legacy tool: its repository is archived and read-only. Current Expo projects use the CLI that ships inside the expo package. Stop installing expo-cli globally; run npx expo start in a project, and create projects with npx create-expo-app@latest on a Node.js LTS release.

  • Applies to current Expo SDK, Node.js 22, Node.js 24, npm 10
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    See whether a legacy global expo-cli is installed, and which Node.js you run. The local CLI needs neither a global install nor an old Node.js.

    node --version
    npm ls -g --depth=0
  2. 2Match what you see, then jump to its fix

    1. 1Your tutorial or script runs expo start or expo init after a global installYou are using the legacy global CLIFix
    2. 2expo init fails because there is no global CLIYou need a new project and are following an old init stepFix

What does the error look like?

  • npm install expo-cli --global fails
  • The legacy expo-cli does not support Node +17

Cause 1 of 2

You are using the legacy global CLI

1Check

The expo-cli repository says it holds packages of the legacy global Expo CLI, and was archived by its owner in January 2024. The modern CLI is included in the expo package and needs no separate install.

npm ls -g --depth=0 | grep expo

2Fix

Remove the global package and use the local CLI from the project folder.

npm uninstall --global expo-cli
npx expo start

3Verify

The dev server starts from the project's own expo package.

npx expo --version

Confirmed by github.com

Did this fix it?

Cause 2 of 2

You need a new project and are following an old init step

1Check

Project creation has its own tool now. The create-a-project guide lists create-expo-app for npm, yarn, pnpm and bun, and asks for Node.js LTS.

node --version

2Fix

Create the project with create-expo-app on a Node.js LTS release, then start it with the local CLI.

npx create-expo-app@latest my-app
cd my-app
npx expo start

3Verify

The dev server prints its QR code and the development URL.

npx expo start

Confirmed by docs.expo.dev

Did this fix it?

How do I stop it coming back?

  • Use npx expo in project scripts, so every machine uses the CLI version pinned in package.json.
  • Run Node.js LTS for new Expo projects, as the Expo guide recommends.
  • Do not copy a global-install step from an old tutorial; check the date and the Expo docs first.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

Expo says it is unable to find expo in this project

Unable to find expo in this project - have you run yarn / npm install yet?

The Expo CLI ships inside the expo package, so the project must have expo as a dependency and installed in its own node_modules.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.