Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

npx ignite-cli new fooapp hangs on "Cleaning up Expo install"

See original GitHub issue

What’s going on?

Attempting to initialize a new expo project, it just hangs on “Cleaning up Expo install”. Left it for hours, and it never completed. When I look at the package.json, none of it is expo-related, it’s all react native stuff.

I can can successfully create and run an app using the vanilla expo-cli

· · · · · · · · · · · · · · · · · · 🔥 Ignite 🔥 · · · · · · · · · · · · · · · · · ·

    █ Creating fooapp using Ignite 7.0.7
    █ Powered by Infinite Red - https://infinite.red
    █ Using expo-cli
    ────────────────────────────────────────────────

 [object Object]
    - Igniting app npx expo-cli@4 init fooapp --template C:\Users\blahblah\AppData\Local\npm-cache\_npx\e31027f3785124a8\node_modules\ignite-cli\boilerplate --non-interactive        
    🔥 Igniting app
 - Downloading and extracting project files.

 √ Downloaded and extracted project files.

 [10:25:13] 🧶 Using Yarn to install packages. Pass --npm to use npm instead.

    - Summoning Expo CLI - Installing JavaScript dependencies.

    | Summoning Expo CLI > yarn install

    - Summoning Expo CLI yarn install v1.13.0

 info No lockfile found.

 [1/4] Resolving packages...

    - Summoning Expo CLI [2/4] Fetching packages...

    \ Summoning Expo CLI info fsevents@2.3.2: The platform "win32" is incompatible with this module.
info "fsevents@2.3.2" is an optional dependency and failed compatibility check. Excluding it from installation.

 info fsevents@1.2.13: The platform "win32" is incompatible with this module.
info "fsevents@1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation.

 [3/4] Linking dependencies...

    - Summoning Expo CLI [4/4] Building fresh packages...

    - Summoning Expo CLI success Saved lockfile.

 $ node ./bin/postInstall

    / Summoning Expo CLI patch-package 6.2.2

 Applying patches...

    / Summoning Expo CLI 
✔︎ Solidarity checks valid

    / Summoning Expo CLI Jetifier found 1263 file(s) to forward-jetify. Using 12 workers...

    \ Summoning Expo CLI Done in 114.09s.

 √ Installed JavaScript dependencies.

 - Installing CocoaPods...

 √ Skipped installing CocoaPods because operating system is not on macOS.



 ✅ Your project is ready!


    🪔  Summoning Expo CLI
    - Cleaning up Expo install To run your project, navigate to the directory and run one of the following yarn commands.

- cd fooapp
- yarn start # you can open iOS, Android, or web from here, or run them directly with the commands below.
- yarn android
- yarn ios # requires an iOS device or macOS for access to an iOS simulator
- yarn web

    \ Cleaning up Expo install

Steps to reproduce

npx ignite-cli new fooapp --expo --debug
Wait for hours - never completes

npx ignite-cli doctor results:

System
  platform           win32         
  arch               x64           
  cpu                12 cores       Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
  directory          foo   D:\blahblah\git\foo

JavaScript (and globally-installed packages)
  node               16.4.2       C:\Program Files\nodejs\node.EXE
  npm                7.18.1       C:\Program Files\nodejs\npm.CMD
    expo-cli         4.7.3       
    npm              7.18.1      
  yarn               1.13.0       C:\Users\blahblah\AppData\Roaming\npm\yarn.CMD
    serve            10.1.2      

Ignite
  ignite-cli         7.0.7        C:\Users\blahblah\AppData\Local\npm-cache\_npx\e31027f3785124a8\node_modules\.bin\ignite.CMD
  ignite src         build        C:\Users\blahblah\AppData\Local\npm-cache\_npx\e31027f3785124a8\node_modules\ignite-cli\build

Android
  java               -            null
  android home       -            undefined