Ignite: Getting an error - /usr/local/lib/node_modules/ignite-cli/node_modules/gluegun/build/index.js:13

Created on 17 Jan 2021 · 3Comments · Source: infinitered/ignite

What's going on?

apple@Apples-MacBook-Pro Template % npx ignite-cli new PizzaApp

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

█ Creating PizzaApp using Ignite 6.1.1
█ Powered by Infinite Red - https://infinite.red
█ Using react-native-cli
────────────────────────────────────────────────

🔥 Igniting app
☕️ Baking CocoaPods
/usr/local/lib/node_modules/ignite-cli/node_modules/gluegun/build/index.js:13
throw up;
^

Error: spawn yarn ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
at onErrorNT (internal/child_process.js:465:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
errno: -2,
code: 'ENOENT',
syscall: 'spawn yarn',
path: 'yarn',
spawnargs: [ 'format' ]
}

Steps to reproduce

Type this command
npx ignite-cli new PizzaApp

ignite doctor results:

System
platform darwin
arch x64
cpu 8 cores Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
directory Template /Users/juggernaut/Desktop/Template

JavaScript (and globally-installed packages)
node 14.14.0 /usr/local/bin/node
npm 6.14.9 /usr/local/bin/npm
expo-cli 4.0.8
ignite-cli 6.1.1
npm 6.14.9
react-native-cli 2.0.1
yarn - not installed

Ignite
ignite-cli 6.1.1 /usr/local/bin/ignite
ignite src build /usr/local/lib/node_modules/ignite-cli/build

Android
java 1.8.0_265 /usr/bin/java
android home - /Users/juggernaut/Library/Android/sdk

iOS
xcode 12.3
cocoapods 1.9.3 /usr/local/bin/pod

Source

Kailash23

Most helpful comment

We've had the same issue in our team and managed to make it work after few hours of research and errors together with @CezaryKnapik.

Before all check if you have global dependencies of your package managers (better use both) yarn global list and npm -g ls and proceed with steps accordingly.

If you have ignite-cli installed globally, make sure you removed the old version and the install a fresh one. (not sure if it really helped, but i did it before the 2 step).
If you have react-native-cli or react-native globally installed, remove it. After that install @react-native-community/cli globally (i've used a specific version @4.13.1). It will have a fresh react-native-cli tool in it (looks like they've migrated, more on this here https://github.com/react-native-community/cli)
After that npx ignite-cli new MyApp worked like a charm. I've also updated node, npm and yarn versions to the latest, but i don't think it had any influence on the matter :)

I hope our team's struggles will save you some time.

bohdan-vasylenko on 22 Jan 2021

👍4 🚀2 ❤1 🎉1

All 3 comments

I am having the same issue. I already have yarn installed.

SophiaBelkin on 19 Jan 2021

We've had the same issue in our team and managed to make it work after few hours of research and errors together with @CezaryKnapik.

Before all check if you have global dependencies of your package managers (better use both) yarn global list and npm -g ls and proceed with steps accordingly.

If you have ignite-cli installed globally, make sure you removed the old version and the install a fresh one. (not sure if it really helped, but i did it before the 2 step).
If you have react-native-cli or react-native globally installed, remove it. After that install @react-native-community/cli globally (i've used a specific version @4.13.1). It will have a fresh react-native-cli tool in it (looks like they've migrated, more on this here https://github.com/react-native-community/cli)
After that npx ignite-cli new MyApp worked like a charm. I've also updated node, npm and yarn versions to the latest, but i don't think it had any influence on the matter :)

I hope our team's struggles will save you some time.

bohdan-vasylenko on 22 Jan 2021

👍4 🚀2 ❤1 🎉1

Beautiful @bohdan-vasylenko , worked like a charm <3