ignite
ignite copied to clipboard
infinitered
npx ignite-cli new fooapp hangs on "Cleaning up Expo install"
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 [email protected]: The platform "win32" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "win32" is incompatible with this module.
info "[email protected]" 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
@growlycode Hm, I was able to spin one up, albeit a lot slower than it should have been.
doctor
System
platform darwin
arch x64
cpu 16 cores Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
directory Temp /Users/jh/Code/Temp
JavaScript (and globally-installed packages)
node 16.4.2 /usr/local/bin/node
npm 7.18.1 /usr/local/bin/npm
appium-doctor 1.15.3
appium 1.17.1
npm 7.18.1
pure-prompt 1.11.0
yarn 1.22.10 /usr/local/bin/yarn
create-next-app 9.4.4
detox-cli 17.11.0
firebase-tools 9.3.0
ios-deploy 1.11.4
react-native-cli 2.0.1
ts-node 8.8.2
typescript 3.8.2
vercel 21.3.3
Ignite
ignite-cli 7.0.6 /usr/local/bin/ignite
ignite src src /Users/jh/Code/ignite-cli/src
Android
java 1.8.0_232 /usr/bin/java
android home - /Users/jh/Library/Android/sdk
iOS
xcode 12.5.1
cocoapods 1.10.1 /usr/local/bin/pod
@growlycode Hm, I was able to spin one up, albeit a lot slower than it should have been.
@jamonholmgren Not sure, I just retried it with the exact same result - 12 hours later and it hadn't completed or spat out any errors. Not the quick "get up and running" thing I had planned. I'm using Windows, if that makes a difference.
Any other suggestions for debugging?
Mine is hanging at Unboxing NPM dependencies. It never completes.
Ignite 7.0.8
On MacOS 2.3 GHz Macbookpro( 8-Core Intel Core i9, 64 GB 2667 MHz DDR4)
I just tried on Windows 10 and got the same hang on Cleaning up Expo install
Also side note, there are no docs of quick start guides or how to run up and view in a (browser, android, ios) command, even some of the links in the main readme link to paywall'd content.
same here, hanging at Unboxing NPM dependencies. It never completes.
I turned on debugging, it is hung on this line
⠦ Unboxing NPM dependencies Jetifier found 1415 file(s) to forward-jetify. Using 8 workers...
it looks like it happens when I run with --expo argument.
same here, stuck at "Cleaning up Expo Install"
The project seams ready but it never ends :(
Npx Ignite-cli doctor
Same here. I really hope this bug gets fixed soon. Ignite seems like it's the perfect boilerplate.
The tricky thing is that if you run the same command in Ubuntu in Windows (WSL), it works like a charm, is it related to windows only?
The tricky thing is that if you run the same command in Ubuntu in Windows (WSL), it works like a charm, is it related to windows only?
Great discovery, it works fine within the wsl container but not if you try to run it on an attached ntfs volume.
just ran into this on windows. non-expo went through fine --expo stuck on cleaning up expo install. there is constant disk usage with Git for Windows process and its been a lot longer than it should and still going... the folder is at 700mb now
I've tried bypassing the immediate problem so that the ignite-cli finishes the install. The resulting app runs, but is not stable when making changes, i.e. I tried implementing bottom tab navigation and none of the tab contents work. maybe this means Git gets stuck on something related to react-navigation or something else that interacts with react-navigation?
Reading through this and having had my own issues I'm going to venture a guess. I think it may have something to do with the workaround in #1776 & #1781. (since .gitignore was changed) I'm basing this on your report that Git disk usage is off the charts, and when I open VSCode I'm seeing 4K+ changes. Possibly the git init for HEAD needs to be reordered if --expo flag is in place? Otherwise it seems that git is running during the CLI cleanup to swap to an Expo app.
edit: As a workaround for myself after I finally did get into the project I manually deleted the hidden .git file in windows and started over with a new git init && git commit -m "init commit"
Having the same problem with --expo flag on Windows 10. Please fix this.
`PS L:\Work\React Native\ignite> npx ignite-cli new PizzaApp --expo
· · · · · · · · · · · · · · · · · · 🔥 Ignite 🔥 · · · · · · · · · · · · · · · · · ·
█ Creating PizzaApp using Ignite 7.9.0
█ Powered by Infinite Red - https://infinite.red
█ Using expo-cli with yarn
█ Bundle identifier: com.PizzaApp
────────────────────────────────────────────────
🔥 Igniting app
🪔 Summoning Expo CLI
| Cleaning up Expo install
`
Edit : I ran the cmd on my Git Bash and it took considerable time but at least it got past the hung up 'Cleaning' process `Palash@Palash-PC MINGW64 /l/Work/React Native/ignite/PizzaApp (master) $ npx ignite-cli new PizzaApp --expo
· · · · · · · · · · · · · · · · · · 🔥 Ignite 🔥 · · · · · · · · · · · · · · · · · ·
█ Creating PizzaApp using Ignite 7.9.0
█ Powered by Infinite Red - https://infinite.red
█ Using expo-cli with yarn
█ Bundle identifier: com.PizzaApp
────────────────────────────────────────────────
🔥 Igniting app
🪔 Summoning Expo CLI
🎫 Cleaning up Expo install
🧶 Unboxing npm dependencies
🗄 Backing everything up in source control
Ignite CLI ignited PizzaApp in 2385.7s
To get started:
cd PizzaApp
yarn start
Need additional help?
Join our Slack community at http://community.infinite.red.
Now get cooking! 🍽 · · · · · · · · · · · · · · · · · · 🔥 Ignite 🔥 · · · · · · · · · · · · · · · · · ·`
There has been a lot of changes since this issue last had activity. This is going to be closed for now, but please re-open if this still needs attention.
