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?Short answer
The Expo CLI ships inside the expo package, so the project must have expo as a dependency and installed in its own node_modules. The error means one of three things: you are not in the project folder, node_modules was never installed, or expo is not in package.json. Check with npm ls expo.
Fix it fast
1Find out which cause you have
From the folder you run the command in, check that package.json is there and whether npm sees expo.
ls package.json npm ls expo2Match what you see, then jump to its fix
- 1
ls package.json says: No such file or directoryYou are not in the project folderFix - 2
package.json lists expo but node_modules is missingnode_modules was never installed (fresh clone, or the folder was deleted)Fix - 3
grep finds no "expo" line in package.jsonexpo is not in package.json at all (a plain React Native project)Fix
- 1
What does the error look like?
Unable to find expo in this project - have you run yarn / npm install yet?
Cause 1 of 3
You are not in the project folder
1Check
npm and the Expo CLI work on the project in the current folder, so a parent or sibling folder gives nothing to find.
pwd
ls package.json2Fix
Change into the folder that holds package.json, then run the command again.
cd path/to/my-app
npx expo start3Verify
The dev server starts and prints the QR code.
npx expo startConfirmed by docs.npmjs.com
Cause 2 of 3
node_modules was never installed (fresh clone, or the folder was deleted)
1Check
npm install puts the dependencies from package.json into the local node_modules folder; until it runs, the expo package is not on disk.
grep '"expo"' package.json
ls node_modules/expo 2>&1 | head -n 22Fix
Install the dependencies.
npm install3Verify
The folder node_modules/expo now exists and npm ls expo shows a version.
npm ls expoConfirmed by docs.npmjs.com
Cause 3 of 3
expo is not in package.json at all (a plain React Native project)
1Check
The Expo docs state that the Expo CLI is included in the expo package, so a project without that dependency has no npx expo to run.
grep '"expo"' package.json2Fix
Add the expo package as a dependency; npm saves a package into dependencies by default. Then follow Expo's install guide for the exact SDK version your React Native version needs.
npm install expo3Verify
The CLI now runs from the project.
npx expo --helpConfirmed by raw.githubusercontent.com
How do I stop it coming back?
- Run npm install (or your package manager's install) after every clone or branch switch that changes package.json.
- Commit package.json and the lock file, never node_modules.
- Start the server with npx expo start from the project root only.
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
appium driver install uiautomator2 fails or the driver will not start
Error installing uiautomator2 driver
Run appium driver install uiautomator2 with the Appium server stopped, on a Node.js and npm version Appium supports (Node ^20.19, ^22.12 or 24+, npm 10+).
3 causes, each with a fixMobile apps
Appium returns 'The requested resource could not be found' (404)
http://localhost:4723/wd/hub
The client is calling a URL the server does not serve.
2 causes, each with a fixMobile apps
Capacitor does not find index.html for a Vue app inside Laravel
the web app files are not found by Capacitor after npx cap sync
Capacitor copies the folder named in webDir, and that folder must hold the final index.html.
3 causes, each with a fixMobile apps
Expo cannot start the Android emulator: spawn adb ENOENT
spawn adb ENOENT
ENOENT means the tool that launched adb could not find an executable named adb on your PATH.
3 causes, each with a fixMobile apps
npm install --global expo-cli fails, or the legacy expo-cli will not run on new Node.js
The legacy expo-cli does not support Node +17
The global expo-cli is the legacy tool: its repository is archived and read-only.
2 causes, each with a fixMobile apps
FCM rejects the message with INVALID_ARGUMENT
HTTP 400 from fcm.googleapis.com/v1/projects/PROJECT_ID/messages:send
INVALID_ARGUMENT is HTTP 400: FCM did not accept the request parameters.
3 causes, each with a fix